a2a-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| A2A_AGENT_URL | No | Default A2A agent endpoint (also overridable per tool call). | http://localhost:8001 |
| A2A_TIMEOUT_SECONDS | No | HTTP client timeout — raise this for slow/long-running agents. | 300 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_agent_cardB | Fetch capabilities (name, description, skills) of an A2A agent. |
| send_a2a_messageA | Send a message to an A2A agent and return its final text response. The response ends with an Long-running agent pipelines are expected: progress notifications are emitted while the task runs, so tune A2A_TIMEOUT_SECONDS rather than treating a slow response as a hang. If the call does time out after the task started, the error names the task_id -- the task keeps running server-side and get_a2a_task can retrieve its result. |
| get_a2a_taskA | Fetch the current state and result of a previously started A2A task. Use this when send_a2a_message timed out or errored after the task had
already started: the task keeps running server-side, and this retrieves
its status and any output by the task_id from the error message or the
|
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 3 tools
Each tool has a distinct purpose: send_a2a_message sends messages, get_a2a_task retrieves task state, get_agent_card fetches agent metadata. No overlap in functionality.
All tools follow a consistent verb_noun pattern with snake_case (get_a2a_task, get_agent_card, send_a2a_message). The naming is predictable and uniform.
Three tools is appropriate for a minimal A2A bridge: send message, poll task result, and discover agent capabilities. The scope is well-defined and not over- or under-tooled.
The set covers core interactions (send, poll, discover) but lacks a cancel or list tasks operation. Minor gap, but agents can work around by polling for completion.