mcp-a2a-documentation
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_documentationA | Search A2A (Agent2Agent) protocol documentation by keyword query. Args:
query: Search terms to find in the documentation. Supports
full-text search with stemming (e.g., "authenticate" matches
"authentication", "authenticated").
section: Optional section to filter results. Common sections
include 'root' (top-level pages such as the specification
and community pages), 'topics' (core concepts), 'tutorials',
and 'sdk'.
source: Optional documentation source to filter results. Currently
only 'a2a' (a2aproject/A2A Returns: JSON-formatted search results with title, URL, snippet, and relevance score. |
| read_documentationA | Read the full content of a specific A2A protocol documentation page. Args: path: The relative path to the documentation file, prefixed with the source name (e.g., 'a2a/topics/what-is-a2a.md' or 'a2a/specification.md'). This path is returned in search results. Returns: The full markdown content of the documentation page, or an error message if the page is not found. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are completely distinct: one searches for relevant documentation pages, the other retrieves the full content of a specific page. There is no overlap in their functionality.
Both tool names follow a consistent verb_noun pattern: search_documentation and read_documentation. The naming style is uniform and predictable.
With only two tools, the server feels somewhat sparse. However, search and read are the core operations for documentation access, so the count is reasonable even though it falls at the low end of the typical range.
The tool surface covers the main workflow: discover pages via search, then fetch full content via read. A minor gap is the lack of a direct way to list all documents without performing a search, but this can be worked around.