Skip to main content
Glama

zaira_get_docs

Read-onlyIdempotent

Retrieve reference documentation for the Zaira Guide API and MCP server on demand.

Topics:

  • getting_started — how to connect via MCP or REST, first queries

  • endpoints — full REST endpoint reference with parameters

  • mcp_tools — MCP tool reference with when-to-use guidance and a routing matrix

  • schema — the tool entry schema

  • errors — error taxonomy for REST (RFC 9457) and MCP (JSON-RPC)

Call with no topic to get an index of available topics.

Returns: the requested topic as a Markdown-KV block. With no topic, returns an index listing all available topics with short descriptions; call again with the relevant topic for the full content.

Examples (topic selection):

  • "How do I call the REST API?" → {topic: "getting_started"}

  • "What parameters does /tools accept?" → {topic: "endpoints"}

  • "What fields are in a tool entry?" → {topic: "schema"}

  • "What error shapes do I handle, and what are the recovery steps?" → {topic: "errors"}

  • "Which MCP tool fits my task?" → {topic: "mcp_tools"}

Edge cases:

  • No topic argument is valid — you get the index. This is the deferred-loading path; don't load every topic at once.

  • Topic must match the enum exactly (lowercase, underscore). "getting-started" with a hyphen is rejected as an unknown parameter.

Risk: read-only, closed-world, idempotent — no state change possible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional topic. One of: getting_started, endpoints, mcp_tools, schema, errors. Omit to get an index of available topics.

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark readOnlyHint, idempotentHint, destructiveHint. Description reinforces with explicit risk statement 'read-only, closed-world, idempotent — no state change possible', adding clarity beyond 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?

Well-structured with sections for topics, examples, edge cases, and risk. Front-loaded with purpose. Every sentence is informative with no redundancy or waste.

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?

With one optional parameter fully described in schema, return value explained (Markdown-KV block or index), and coverage of all topics, this is complete for a documentation retrieval tool despite no output schema.

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

Parameters5/5

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

Schema provides enum and description for 'topic'. Description adds examples, edge cases (exact matching required), and explains behavior when omitted, providing meaning beyond the schema.

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?

Description uses specific verb 'Retrieve' and resource 'reference documentation for the Zaira Guide API and MCP server', clearly distinguishing it from sibling tools that deal with tools or categories.

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?

Provides when-to-use guide with topic enumeration, examples for each topic, edge cases (no topic, exact match required), and implicitly distinguishes from siblings by focusing on documentation retrieval.

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool has a distinct purpose: comparing tools, retrieving docs, getting a single tool, listing categories, and searching. There is no overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent 'zaira_verb_noun' pattern (e.g., compare_tools, get_docs). The naming is uniform and predictable.

Tool Count5/5

5 tools is well-scoped for a guide/reference server. Each tool serves a clear function without excessive overlap or missing coverage.

Completeness5/5

The tool set covers all expected operations for a tool guide: browsing categories, searching, retrieving details, comparing, and getting documentation. There are no obvious dead ends.

Resources