Skip to main content
Glama
mcp-a2a-documentation

mcp-a2a-documentation

by martoc

search_documentation

Search A2A protocol documentation by keyword to find relevant specifications, tutorials, and SDK references.

Instructions

Search A2A (Agent2Agent) protocol documentation by keyword query.

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": {
      "query": "<query>"
    },
    "name": "search_documentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default: 10, max: 50).
queryYesSearch terms to find in the documentation. Supports full-text search with stemming (e.g., "authenticate" matches "authentication", "authenticated").
sourceNoOptional documentation source to filter results. Currently only 'a2a' (a2aproject/A2A `docs/` directory) is indexed.
sectionNoOptional section to filter results. Common sections include 'root' (top-level pages such as the specification and community pages), 'topics' (core concepts), 'tutorials', and 'sdk'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.4
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return (default: 10, max: 50)."
    • addedInput schema / properties / query / description
      Added value: +"Search terms to find in the documentation. Supports\n   full-text search with stemming (e.g., \"authenticate\" matches\n   \"authentication\", \"authenticated\")."
    • addedInput schema / properties / section / description
      Added value: +"Optional section to filter results. Common sections\n     include 'root' (top-level pages such as the specification\n     and community pages), 'topics' (core concepts), 'tutorials',\n     and 'sdk'."
    • addedInput schema / properties / source / description
      Added value: +"Optional documentation source to filter results. Currently\n    only 'a2a' (a2aproject/A2A `docs/` directory) is indexed."
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not confirm this is a read-only operation, does not describe ranking/relevance ordering, pagination, or any limits beyond what the schema already states, leaving behavior mostly undisclosed.

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

Conciseness4/5

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

A single, front-loaded sentence with no filler. It is efficient, though its brevity borders on under-specification for a multi-parameter search tool.

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

Completeness3/5

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

An output schema exists, so return values needn't be explained, and the schema richly documents all parameters. However, with no annotations and no routing guidance relative to read_documentation, an agent lacks the usage context needed to choose this tool confidently.

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%, so all four parameters (query, limit, source, section) are already documented in the schema with examples and defaults. The description only restates that search is keyword-based, adding no parameter semantics beyond the schema; baseline 3 applies.

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

Purpose4/5

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

States a specific verb ("Search") plus resource ("A2A protocol documentation") and the retrieval method ("keyword query"). It implicitly contrasts with the sibling read_documentation (search vs. direct read), though it never names that sibling.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance, and the sibling read_documentation is never mentioned. An agent must infer that this is the discovery tool to use before knowing which document to read.

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

Deploy Server

Other Tools