guide-registry

Search guides, or refuse with the nearest owned

search_guides

Read-only

Search published guides by topic. Returns matches, or a structured refusal with the nearest owned guides and the missing topic. No model call. Filter by persona or category.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "search_guides"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Topic or question in plain language. No model call — matched against registry taxonomy and the capability spine.
`limit`	No	Cap hits returned. Default 10, max 20.
`persona`	No	Audience filter. A miss that fails this rule is a structured refusal.
`category`	No	Subject shelf filter. A miss that fails this rule is a structured refusal.

Output Schema

Name	Required	Description	Default
`query`	Yes
`guides`	Yes
`covered`	Yes
`filters`	Yes
`nearest`	Yes
`suggest`	Yes
`api_version`	Yes
`missing_topic`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the read-only annotation, the description discloses valuable behavior: 'Returns matches, or a structured refusal with the nearest owned guides and the missing topic' and 'No model call' warn the agent about cost and fallback behavior. This is substantive behavioral context not present in the annotations.

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?

Three terse sentences front-load the operation, then describe the return/refusal behavior footnote, then the filters. Every sentence earns its place with no filler or repetition.

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

Completeness5/5

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

For a 4-parameter read-only search tool with a full input schema and an output schema, the description is complete enough for correct invocation. It covers the main purpose, miss behavior, the model-call constraint, and the optional filters; remaining details live in the structured schemas.

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?

Input schema coverage is 100%, so the schema already documents all four parameters. The description adds only a light restatement of the persona/category filters and 'No model call', which appears in the schema's q description too; no deeper semantic value is added.

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 names a specific verb ('Search'), a resource ('published guides'), and a query mode ('by topic'), which clearly distinguishes it from list_guides and get_guide. The title and body also convey the refusal behavior, so the agent knows this is a search-with-miss-handling tool, not a simple enumerator.

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 gives clear context for when to use it — topic-based search with persona/category filters — but it never names siblings like list_guides or get_guide, nor does it state when-not-to-use it. The distinction from other guide tools is implied rather than explicit.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?