Skip to main content
Glama
alvintayzhenwei

a2a-mcp-connector

by alvintayzhenwei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
a2a_validateA

Validate ANY standard A2A endpoint's Agent Card and return a readable report (valid?/checks/warnings). agent_card_url is the full served card URL (e.g. .../.well-known/agent-card.json); bearer is optional (only needed if the card route requires auth). Nothing is connected or sent — this only fetches and inspects the card. The bearer is never echoed back.

a2a_connectA

Connect to a standard A2A endpoint and start streaming its turns. Validates the Agent Card first and REFUSES to connect if it isn't usable (returns the validator report). On success, starts a background session and returns immediately — then call a2a_wait_turn for the first prompt. bearer is optional (pass it only if the endpoint requires auth). Neither the card URL's contents nor the bearer are echoed back.

a2a_wait_turnA

Wait for the next turn's prompt, bounded by max_seconds (default 30) so this never hangs indefinitely. Returns the prompt text once it's your turn, "the session is over." once the remote agent finishes, an "Error: ..." string if the session broke, or "No turn yet — call a2a_wait_turn again." if the window elapsed first (just call it again). Show whatever this returns to your human and get their actual reply before calling a2a_send.

a2a_sendA

Submit your reply to the CURRENT pending turn (call a2a_wait_turn first to see the prompt). Returns immediately; call a2a_wait_turn again for the next turn. Rejected if it isn't your turn yet.

a2a_statusA

A quick snapshot: connected? a turn pending? session over? any error? Useful to re-orient after a gap in the conversation.

a2a_leaveA

Disconnect: cancel the background driver and close the session cleanly. Safe to call even if not connected.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.5/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a distinct responsibility: validate checks the Agent Card, connect establishes the session, send/wait_turn handle messaging, status reports state, and leave tears down. No functional overlap or ambiguity exists.

Naming Consistency4/5

All tools use the a2a_ prefix and mostly use verb-led names like connect, send, leave, and validate. The sole exception is a2a_status, which is a noun rather than an imperative verb, but it remains clear and aligned with the overall pattern.

Tool Count5/5

Six tools is appropriate for a focused A2A connector: validation, connection, turn-based messaging, status polling, and disconnection. The toolset is lean without missing necessary lifecycle operations.

Completeness5/5

The toolset covers the full A2A session lifecycle: validate, connect, send, wait for turn, check status, and leave. No essential operation for interacting with a remote agent over this protocol appears to be missing.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources