Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

search_a2a_agents

Read-only

Find A2A agents you can delegate a task to.

Args:
    intent: Natural-language description of the task to delegate.
    top_k: Max agents to return (1-20).
    x402_only: When true, only return agents that advertise x402 payment.

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": "search_a2a_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_kNoMax agents to return (1-20).
intentNoNatural-language description of the task to delegate.
x402_onlyNoWhen true, only return agents that advertise x402 payment.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / intent / description
      Added value: +"Natural-language description of the task to delegate."
    • addedInput schema / properties / top_k / description
      Added value: +"Max agents to return (1-20)."
    • addedInput schema / properties / x402_only / description
      Added value: +"When true, only return agents that advertise x402 payment."
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without the description. The description adds the delegation framing and the x402 filtering concept but says nothing about ranking, scoring, empty-result behavior, or what happens when intent is null — which matters since all three params are optional.

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

Conciseness3/5

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

The opening sentence is well front-loaded, but the entire Args section duplicates the input schema word for word, so a meaningful share of the text earns no place.

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

Completeness3/5

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

An output schema exists and annotations cover safety, so the description needn't explain return values. What is missing is the differentiator against the crowded sibling set of search tools and any note on behavior when intent is omitted — a gap for an all-optional-parameter tool.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The Args block in the description is a verbatim copy of the schema descriptions and adds no new semantics, such as what a good intent string looks like or how top_k interacts with result quality.

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

Purpose4/5

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

The first sentence names a concrete verb and resource (find A2A agents) plus the use case (delegating a task), which is clear on its own. However, it never distinguishes itself from the many sibling search tools (search_mcp_servers, search_resources, search), so an agent cannot tell from the description alone why it would pick this one.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternatives among the sibling search tools. The delegation framing implies a context, but the agent must infer it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.