Skip to main content
Glama

x402 market stats

x402_market_stats
Read-onlyIdempotent

Statistics of the verified x402 seller set (sellers by source and evidence, median declared price; not the whole market) and 30-day x402 market totals from x402stats (CC BY 4.0, attributed in the answer). No parameters. Market-wide totals only, no per-service rows; for individual services use search_x402_services; for this host's own tools use list_paid_data_products.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations it discloses provenance (data from x402stats), a licensing obligation the agent must honor ('CC BY 4.0, attributed in the answer'), and a scope caveat about what the seller set actually represents. These are actionable behavioral facts the annotations cannot convey.

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?

Everything is front-loaded — what it returns, then scope caveats, then sibling routing — with no filler sentences. The heavy nested parentheses make it slightly denser to parse than necessary, but no clause is redundant.

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 no output schema, the description does the work of describing what comes back (per-source seller counts, evidence, median declared price, 30-day totals) and adds the attribution duty. The only remaining gap is how 'verified' is defined and how fresh the 30-day window is, which is minor for an aggregate stat tool.

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, which sets the baseline at 4; the description confirms 'No parameters' and needs to add nothing further. There is no parameter meaning left to explain.

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

Purpose5/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: statistics over the 'verified x402 seller set' with named contents (sellers by source and evidence, median declared price) plus 30-day market totals. It also explicitly bounds itself ('not the whole market', 'no per-service rows'), so an agent can distinguish it from search_x402_services and list_paid_data_products without opening a schema.

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

Usage Guidelines5/5

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

It gives both halves of the routing decision: use this for market-wide aggregates, and use search_x402_services for individual services or list_paid_data_products for this host's own tools. It also states 'No parameters', removing any ambiguity about how to invoke 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.

Resources