Skip to main content
Glama

agent-tools (x402 + MCP + A2A directory)

stats

Read-only

High-level stats about the directory: x402 total, healthy count and chains, plus snapshot, the daily digest across x402, MCP and A2A (see directory_stats).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 agent knows this is a safe local read. The description adds useful scope detail by naming exactly which figures come back (totals, healthy count, chains, daily digest), but says nothing about freshness, aggregation window, or cost of the snapshot.

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 sentence that is front-loaded with 'High-level stats about the directory' and then lists the payload. It is dense but every clause carries content; the backticked `snapshot` is slightly awkward without explanation of what the field contains.

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?

With an output schema present and no inputs, the description only needs to convey what kind of data this returns, which it does. The remaining gap is the relationship to `directory_stats`, which is gestured at but not resolved.

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; the baseline of 4 applies. The named fields (x402 total, healthy count, chains, snapshot) are output content rather than inputs.

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 states a specific resource (directory stats) and enumerates the content it surfaces: x402 total, healthy count, chains, and the `snapshot` daily digest across x402/MCP/A2A. It also points at the closest sibling, `directory_stats`, which helps an agent distinguish the two, though it doesn't say explicitly how they differ.

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 parenthetical '(see directory_stats)' implies there is a related tool worth consulting, but it never states when to pick one over the other or what the prerequisite/relationship is. Usage is only implied, not explicit.

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.