Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

directory_stats

Read-only

Daily statistics on the agent-tool ecosystem as seen by our probes.

Args:
    view: "all", "mcp", "x402" or "a2a" to scope the figures to one protocol.
    topic: Optional topic word (e.g. "payment", "weather") to get that topic
        instead: supply per protocol, readiness, best listings, searches.
    month: Optional "YYYY-MM" to get that monthly report instead.
    api_key: Optional account key (free from create_api_key) for complete
        lists when you cannot send the Authorization header.

Returns counts (indexed, reachable, protocol-verified, readiness A/B), one
finding sentence per topic, key facts (x402 prices and networks, MCP and A2A
protocol versions, MCP auth, A2A card signatures, how every listing's
latest probe ended), the most searched terms (view "all"), the snapshot
time, and links to the full JSON snapshot, the daily CSV, the methodology,
the "how many work" page, per-protocol and per-topic pages and the monthly
reports. With an account API key (Authorization: Bearer header or
`api_key`; free from `create_api_key`) the topic and search lists are
complete (10 listings per protocol, up to 100 terms); without one they
are shortened.

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

Input Schema

NameRequiredDescriptionDefault
viewNo"all", "mcp", "x402" or "a2a" to scope the figures to one protocol.all
monthNoOptional "YYYY-MM" to get that monthly report instead.
topicNoOptional topic word (e.g. "payment", "weather") to get that topic instead: supply per protocol, readiness, best listings, searches.
api_keyNoOptional account key (free from create_api_key) for complete lists when you cannot send the Authorization header.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/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. The description adds material behavior beyond that: results are truncated without an account key (10 listings per protocol, up to 100 terms) versus complete with an api_key or Bearer header, which is a real constraint an agent must plan around. It stops short of describing rate limits or caching/refresh cadence of the daily snapshot.

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 purpose is front-loaded and the Returns paragraph is information-dense, but the Args block duplicates the schema definitions word for word, which is dead weight. The closing auth paragraph also repeats the 'free from create_api_key' point already made earlier in Args, so the text is longer than it needs to be.

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?

Since an output schema exists, the tool need not explain return values, but it does so thoroughly (counts, findings, key facts, search terms, snapshot time, links), which errs on the side of completeness rather than omission. Auth behavior and truncation limits are covered, leaving only minor gaps such as the snapshot refresh cadence. Overall the definition is sufficient to call the tool correctly.

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%, and the Args block in the description restates the same view/topic/month/api_key text nearly verbatim, so it adds little semantic value over the schema. The one genuine addition is the api_key note about 'when you cannot send the Authorization header' and its effect on list completeness, which is real but narrow. Baseline 3 is appropriate when the schema already documents every parameter.

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 description opens with a concrete resource and scope: 'Daily statistics on the agent-tool ecosystem as seen by our probes,' and the Args/Returns sections make clear it produces daily or monthly reports scoped by protocol or topic. It is clear what the tool does, though it never explicitly distinguishes itself from the sibling tool named 'stats', leaving that differentiation to inference.

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?

Usage is conveyed indirectly through the parameter explanation: pass view to scope to one protocol, topic to get a topic report, month to get a monthly report. This tells an agent how to shape a call but gives no explicit when-to-use/when-not guidance and no comparison to alternatives like 'stats' or 'search', so the choice between them remains ambiguous.

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.