guide-registry

List the guide registry

list_guides

Read-only

List the bicycle.guide registry — every guide's home, status, access, standard, syndication and grounding, plus the distribution roll-up (including guides homed to a property with no rendering surface).

Input Schema

TableJSON Schema

Name	Required	Description
`home`	No	Filter by owning property, e.g. jobframe, peopleanalyst, penwright.
`limit`	No	Cap the rows returned. Default 100, max 500.
`access`	No	Filter by access: free \| gated.
`domain`	No	Filter by life-domain — the layer ABOVE the subject shelf: work \| life \| play. Derived from the guide's category via content/registry/shelves.json. `rollup.by_domain` lists them.
`fields`	No	Row shape. "compact" returns only slug/title/home/status/access/price_cents/has_artifact/category/domain/personas/canonical_url — no rollup, no registry_meta. "full" returns the entire decorated registry row plus the rollup and registry_meta, as before. Default over this server: "compact".
`series`	No	Filter by guide series — the operational grouping of guides made to be used together, e.g. competencies, penwright-writing, startup-journey, ladder:hr-business-partner.
`status`	No	Filter by status: on \| draft.
`persona`	No	Filter by the audience a guide serves, e.g. people-analytics-professional, aspiring-author, executive-performance-leader. A guide can serve several; this matches any of them.
`category`	No	Filter by subject shelf — the reader-facing topic axis, e.g. field, skills, analytics, writing, comp. Matches the primary category OR a cross-shelf tag.
`standard`	No	Filter by standard: bicycle \| life-stage \| problem-opportunity.
`guide_type`	No	Filter by guide CLASS: career (level-based job guides, their own program) \| capability \| book_profile. Combine with series=ladder:<role> to get one role's whole ladder.
`has_artifact`	No	Only guides that do (true) / do not (false) have a new-design artifact.
`home_unrouted`	No	Only guides whose home has NO rendering surface at all (the distribution gap).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`limit`	Yes
`fields`	Yes
`guides`	Yes
`rollup`	No
`filters`	Yes
`api_version`	Yes
`registry_meta`	No
`total_matching`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 8, 2026

TDQS

A4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered by structured data. The description adds meaningful behavioral context: it returns every guide and includes the distribution roll-up, explicitly including guides whose home property has no rendering surface. This non-obvious inclusion helps an agent understand the tool's reach beyond a simple listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence that names the resource and then adds precise scope in a compact parenthetical. Every element — the field list, the roll-up mention, and the no-rendering-surface inclusion — earns its place by clarifying the tool's coverage without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 13 optional parameters, full schema descriptions, an output schema, and read-only annotations, the description gives enough context for correct selection and invocation. It captures the registry's unusual breadth, though it could optionally say when to prefer sibling listing tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and every parameter carries a concrete explanation with examples, defaults, and enum values where applicable. The description itself does not add parameter-level meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') and names the exact resource ('bicycle.guide registry'), then enumerates what is returned: home, status, access, standard, syndication, grounding, and the distribution roll-up. This clearly distinguishes the tool from siblings like get_guide, list_capabilities, and list_taxonomy by emphasizing the registry-wide listing scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it — whenever you need the full guide registry or its distribution roll-up — but it does not explicitly state when not to use it or name alternatives like list_capabilities or list_taxonomy. The context is reasonably clear, but no exclusions or alternative routing are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All guide-registry tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?