Bundled reference docs
R1-MCP ships a set of curated reference documents that Claude reads on demand
through get_reference. They carry the knowledge that isn’t in the RUCKUS
API spec or the user guide: verified CLI patterns, GraphQL schemas that
introspection can’t reveal, and workflow playbooks proven against real hardware.
You don’t invoke them. Claude fetches the relevant one before doing work that needs it — but knowing what exists tells you what Claude has to work from, and what to ask for by name.
How it works
Section titled “How it works”get_reference with no arguments lists the docs available to you. With a doc
key it returns that document’s table of contents; with a doc and a section it
returns that section’s text.
The tool appears once you have at least one feature enabled, and the listing only shows the docs for features you actually have on.
The catalog
Section titled “The catalog”| Doc key | Feature | What it covers |
|---|---|---|
icx-workflow | ICX | The end-to-end ICX config loop: backup, generate, verify, apply, read back, diff |
icx-bgp-evpn | ICX | BGP-EVPN fabric configuration on FastIron 10.0.20 |
icx-evpn-playbook | ICX | Lab-verified EVPN build and validation playbook |
icx-static-vxlan | ICX | Static VXLAN configuration |
icx-ops-playbook | ICX | Day-two operations on an ICX fabric |
icx-troubleshooting | ICX | ICX switch troubleshooting |
stig-icx-l2s | ICX | DISA STIG validation for ICX layer-2 switches |
stig-icx-router | ICX | DISA STIG validation for ICX routers |
webhooks-setup | Webhooks | Configuring the event receiver in RUCKUS One |
ap-cli-guide | Live CLI | The AP CLI — what it accepts and how output reads |
mop-authoring | Live CLI | Writing a MOP: steps, gates, provenance, rollback |
testbed-workflow | Test Bed | Capture, plan, apply, and restore a test bed |
venue-copy-workflow | Copy | The venue copy pipeline, safety gates, and support matrix |
probe-verify | Probe | Which probe check verifies which class of R1 write |
data-studio | Data Studio | The Superset console recipe, query shapes, and caveats |
gql-analytics | GraphQL | The analytics surface, and IntentAI |
gql-troubleshooting | GraphQL | Client and incident troubleshooting, and Call QoE |
gql-service-guard | GraphQL | Service Validation |
Why some of these exist at all
Section titled “Why some of these exist at all”The GraphQL docs are the only schema source. Introspection is disabled on all
four RUCKUS AI GraphQL services, so there is nothing to probe — see
GraphQL API support. They’re organized by surface rather than
one per service, which is why IntentAI lives in gql-analytics and Call QoE in
gql-troubleshooting.
The ICX docs are the verified-syntax backbone. FastIron CLI is never emitted from memory; it’s checked against the indexed documentation and these playbooks first. See ICX switches and FastIron docs.
data-studio accumulates. Learnings saved with ds_save_note are returned
alongside the bundled data-studio document, so a quirk discovered in one
session is in front of Claude in the next. See
Data Studio dashboards.
See also
Section titled “See also”- Core tools — the always-available tool surface
- Features and feature flags — what enabling a feature adds