Skip to main content
Glama
Sign In
mcp-a2a-bridge

mcp-a2a-bridge

by TonPC64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

a2a_list_agents

Fetch configured A2A agents with their skills and reachability. Use refresh=true to update cached agent cards.

Instructions

List configured A2A agents with their skills and reachability.

Set refresh=true to re-fetch agent cards that were previously cached.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "a2a_list_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the burden. It usefully discloses caching behavior and the effect of refresh, but it does not state that the operation is read-only, describe the return structure, or mention any potential side effects or prerequisites. Some relevant behavior remains implicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: the first states the tool's purpose and result scope; the second explains the only parameter. No filler or duplication of the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple, single optional-parameter list operation, this description is largely complete. It identifies what the result includes, notes the caching behavior, and explains the parameter. A fully explicit return-format statement would be nice, but it is not essential for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It does by explaining that refresh=true re-fetches cached agent cards. It stops short of explaining the exact behavior when refresh is false (e.g., serving from cache), but the meaning is strongly implied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('List'), a clear resource ('configured A2A agents'), and the relevant output facets ('skills and reachability'). It is immediately distinguishable from its siblings, which send messages or manage tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The refresh guidance is clear operational context ('Set refresh=true to re-fetch agent cards that were previously cached'). However, there is no explicit statement about when to prefer this tool over alternatives such as a2a_send_message or a2a_get_task; the distinction is only implied by the name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools