Skip to main content
Glama

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
register_agentC

Register an A2A agent with the bridge server.

Args: url: URL of the A2A agent

Returns: Dictionary with registration status

list_agentsB

List all registered A2A agents.

Returns: List of registered agents

unregister_agentC

Unregister an A2A agent from the bridge server.

Args: url: URL of the A2A agent to unregister

Returns: Dictionary with unregistration status

send_messageA

Send a message to an A2A agent.

Args: agent_url: URL of the A2A agent message: Message to send session_id: Optional session ID for multi-turn conversations

Returns: Agent's response with task_id for future reference

get_task_resultA

Retrieve the result of a task from an A2A agent.

Args: task_id: ID of the task to retrieve history_length: Optional number of history items to include (null for all)

Returns: Task result including status, message, and artifacts if available

cancel_taskC

Cancel a running task on an A2A agent.

Args: task_id: ID of the task to cancel

Returns: Cancellation result

send_message_streamA

Send a message to an A2A agent and stream the response.

Args: agent_url: URL of the A2A agent message: Message to send session_id: Optional session ID for multi-turn conversations

Returns: Stream of agent's responses

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: cancel_task, get_task_result, list_agents, register_agent, send_message, send_message_stream, and unregister_agent all target specific operations in the A2A agent management workflow. The two message-sending tools are differentiated by streaming vs. non-streaming behavior, avoiding confusion.

Naming Consistency5/5

All tools follow a consistent verb_noun naming pattern (e.g., cancel_task, get_task_result, list_agents, register_agent). The naming is uniform across all seven tools, using snake_case throughout without any deviations or mixed conventions.

Tool Count5/5

With 7 tools, the server is well-scoped for managing A2A agents and tasks. Each tool earns its place by covering essential operations like agent registration, message sending, task management, and result retrieval, without being overly sparse or bloated.

Completeness4/5

The tool set provides strong coverage for core A2A agent workflows, including agent lifecycle (register/unregister/list), task management (cancel/get result), and communication (send message with and without streaming). A minor gap exists in lacking a tool to directly list or manage tasks without prior knowledge of task IDs, but agents can work around this using existing tools.

Maintenance

ActivityInactive
ResponsivenessNo issues