Skip to main content
Glama

Search Docs

search-docs
Read-onlyIdempotent

Searches the whole standard, every section of every page and every checklist rule, and returns the best matches: where each one is, a short excerpt, and for rules, their ID, level and scope.

WHEN TO USE: to find where a topic is covered when you don't know the page or the section, like "focus after delete", "spinner", "aria-pressed" or "dark mode". Then read a section with get-page, or rules with list-rules. WHEN NOT TO USE: to list a component's rules, use list-rules. To see which components there are, use list-components.

Search for a few specific words rather than a whole question.

Input Schema

NameRequiredDescriptionDefault
typeNoOnly search sections, or only rules.
limitNoHow many results to return, at most.
queryYesA few words, like "focus after delete" or "aria-pressed".
componentNoOnly search this page and its rules, like button or design-tokens.

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYesHow many sections and rules match, of which the best come first.
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "popover",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "field",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "radio-group",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "popover",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "radio-group",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "radio-group",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "card",
      -  "checkbox-group",
      -  "checkbox",
      -  "dialog",
      -  "input",
      -  "spinner",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "radio-group",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  5. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "dialog",
      -  "switch",
      -  "textarea",
      -  "tooltip",
      -  "checkbox-group"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "card",
      +  "checkbox-group",
      +  "checkbox",
      +  "dialog",
      +  "input",
      +  "spinner",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  6. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "textarea",
      -  "tooltip",
      -  "checkbox-group"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "dialog",
      +  "switch",
      +  "textarea",
      +  "tooltip",
      +  "checkbox-group"
      +]
  7. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "textarea",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "textarea",
      +  "tooltip",
      +  "checkbox-group"
      +]
  8. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "card",
      -  "checkbox",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "textarea",
      +  "tooltip"
      +]
  9. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "switch",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "card",
      +  "checkbox",
      +  "switch",
      +  "tooltip"
      +]
  10. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input",
      -  "tooltip"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "switch",
      +  "tooltip"
      +]
  11. Changed1 schema field changed
    • changedInput schema / properties / component / enum
      Previous value: -[
      -  "introduction",
      -  "roadmap",
      -  "mcp-server",
      -  "agent-plugin",
      -  "design-tokens",
      -  "button",
      -  "spinner",
      -  "input"
      -]New value: +[
      +  "introduction",
      +  "roadmap",
      +  "mcp-server",
      +  "agent-plugin",
      +  "design-tokens",
      +  "button",
      +  "spinner",
      +  "input",
      +  "tooltip"
      +]
  12. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so safety needs no restating. The description adds real behavioral texture: it says what a result contains (location, excerpt, and for rules ID/level/scope) and warns that short keyword queries outperform long natural-language questions. Return-shape detail is partly redundant with the output schema, which keeps this from a 5.

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?

Front-loaded with the core action, then cleanly partitioned into WHEN TO USE / WHEN NOT TO USE / a query tip. Every sentence carries actionable information; nothing is padding.

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 an output schema and full annotation coverage, the description supplies everything an agent needs: scope, routing to siblings, follow-up reads, and query formulation guidance.

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 coverage is 100% and the enum-constrained filters (type, component) are fully self-documenting, so the schema carries the load. The description adds one useful hint on phrasing the query parameter ('a few specific words rather than a whole question'), but says nothing about limit or component scoping, so baseline 3 applies.

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?

States a specific verb and resource with full scope ('searches the whole standard, every section of every page and every checklist rule') plus a preview of the result shape. It is clearly distinguishable from get-page and list-rules, which read structured slices rather than doing free-text search.

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

Usage Guidelines5/5

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

Explicit WHEN TO USE and WHEN NOT TO USE blocks name the alternatives (get-page, list-rules, list-components) and the conditions that select them, backed by concrete example queries. It even specifies the follow-up path after a search, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.