Skip to main content
Glama

Hunter Pūteanui (hcIfU)

agent_to_agent_guide

Read-onlyIdempotent

Free: how agents find each other, talk, pay and trust - A2A 1.0, MCP and x402 v2, from the makers' own specifications.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description's one genuine addition is 'Free' — an operational fact about cost that annotations do not carry. It still omits what actually comes back (a static document? a pointer list?) and how large it is.

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

Conciseness4/5

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

A single compact line with no padding, and the version scoping (A2A 1.0, x402 v2) is useful up front. The dash-separated list is slightly cryptic but nothing is wasted.

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?

For a zero-param read-only tool with full annotation coverage, the description covers topic and cost but not deliverable shape. With no output schema, it should state that the call returns documentation text rather than an action or lookup result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter-level detail is needed or missing.

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

Purpose3/5

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

The topic is specific (A2A 1.0, MCP, x402 v2 — agent discovery, communication, payment, trust), but there is no verb saying what the tool does with that topic. It reads as a subject label rather than 'returns a reference guide on X,' so an agent can guess the domain but not the action.

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?

No when-to-use guidance and no exclusions. The 'Free:' prefix hints this is a no-cost alternative, but the description never says when to call it instead of siblings like audit_agent_endpoint or list_hunter_services.

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.

Resources