Skip to main content
Glama

Agent Exchange router

What the x402 census holds right now

census_stats
Read-only

No arguments. The size and date of the Agent Exchange x402 census (every paid API endpoint in the Coinbase CDP and PayAI catalogs), where to search it, and how a seller gets listed or featured here.

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

Input 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 safety profile is covered; the description contributes the catalog scope (Coinbase CDP and PayAI) and the fact that the figures are a current snapshot ('right now' via title). It does not describe the shape of the response (counts, dates, URLs) or whether the numbers are live or cached, which is the main behavioral unknown for a stats endpoint. Adds moderate value beyond the annotations, no contradictions.

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 front-loaded sentence with no filler, and the 'No arguments' constraint is stated first so an agent knows immediately it is a parameterless call. The sentence is dense, bundling three disparate deliverables (stats, search location, listing rules), which makes it slightly harder to parse than two shorter sentences would 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?

For a zero-argument, read-only informational tool with no output schema, the description carries the necessary burden by enumerating what comes back and which catalogs are covered. The only real gap is that return format and freshness of the census figures are unspecified, which matters for a tool whose value is its numbers.

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 per the baseline there is nothing the description must disambiguate; the schema coverage is 100% and empty. 'No arguments' is redundant with the empty schema but harmlessly confirms that no call-shaping inputs exist.

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 names the concrete content the tool surfaces: the size and date of the x402 census, where to search it, and how a seller gets listed. The scope (Coinbase CDP and PayAI catalogs) is explicit, so an agent can tell this is an informational/coverage-stats tool rather than a search tool. It is a noun-phrase delivery list rather than a verb+resource statement, which slightly blurs whether it is a stats call or a help call, and it does not name which sibling to use instead.

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?

Opening with 'No arguments' and listing the three things returned implicitly tells an agent when the tool is useful (checking census size/date, locating the right search surface, learning listing/featured rules). However, there is no explicit when-to-use vs when-not-to-use and no reference to the actual sibling tools such as search_all_catalogs or find_resources, even though this tool's 'where to search it' content clearly complements them.

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