A2A MCP Server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| a2a_send_messageA | Send a message to an Agent-to-Agent (A2A) protocol compliant agent. This tool establishes communication with an A2A agent and sends a text message. The agent may respond immediately with a message or return a task object for asynchronous processing. Args:
Returns: JSON response containing either:
The response may include multiple parts (text, images, etc.) depending on the agent's capabilities. Examples:
Error Handling:
|
| a2a_get_taskA | Retrieve the status and details of an A2A task by its ID. This tool fetches information about a previously created task, including its current status, progress, and any generated artifacts. Args:
Returns: JSON response containing task information:
Examples:
Error Handling:
|
| a2a_cancel_taskA | Cancel a running A2A task. This tool requests cancellation of an active task. The agent will attempt to gracefully stop the task execution and update its status to "canceled". Args:
Returns: JSON response confirming the cancellation request:
Note: Cancellation may not be immediate. The task status should transition to "canceled" once the agent completes the cancellation process. Examples:
Error Handling:
|
| a2a_get_agent_cardA | Retrieve an agent's card containing metadata and capability information. This tool fetches the agent card which describes what the agent can do, its configuration, supported features, and other metadata. Args:
Returns: JSON response containing the agent card with:
Agent cards follow the A2A protocol specification and help clients understand how to interact with the agent. Examples:
Error Handling:
|
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 4 tools
Each tool targets a distinct A2A operation: sending messages, retrieving tasks, canceling tasks, and fetching agent cards. There is no meaningful overlap between their purposes, and the descriptions include explicit cross-references to prevent misselection.
All tools follow the same a2a_<verb>_<noun> pattern: a2a_send_message, a2a_get_task, a2a_cancel_task, and a2a_get_agent_card. The naming is uniform, predictable, and clearly indicates the action and resource involved.
Four tools is well-scoped for an A2A protocol server. Each tool covers one essential protocol interaction without unnecessary redundancy or missing core functionality.
The tool set covers the essential A2A workflow: discovering agent capabilities via the agent card, sending messages, checking task status, and canceling tasks. This is a complete surface for the stated purpose of interacting with A2A-compliant agents.