Agent Data API

x402_market_summary

The x402 economy in one call: measured daily spend across the top Bazaar sellers on Base, split into organic, likely wash and known samplers/graders, with 7-day totals, the top categories by spend and the top buyer wallets (addresses, labeled when known). Measured from USDC transfers of $5 or less into each seller's payTo on Base, one UTC day at a time, with the day it covers. Costs $0.005 USDC on Base via x402.

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_summary"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and usefully discloses the measurement method (USDC transfers of $5 or less into payTo on Base, one UTC day at a time), the exact cost ($0.005 USDC via x402), and the output dimensions. It stops short of stating data freshness, read-only nature, or rate limits, so it adds meaningful but incomplete behavioral context.

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?

Three dense sentences, front-loaded with the purpose, and every clause appears to convey substantive output or measurement detail. The slight repetition in 'measured daily spend' and 'Measured from USDC transfers' is minor.

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 no-parameter, no-output-schema summary tool, the description gives enough about return contents (spend splits, 7-day totals, categories, buyer wallets) and methodology for an agent to call it. It is missing only minor behavioral details such as data freshness or read-only status.

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?

Zero-parameter tool, so the rubric baseline is 4. There are no parameters to document and the description correctly does not invent any.

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 verb ('market summary' via 'measured daily spend') and resource (x402 economy / top Bazaar sellers on Base), and enumerates what is split and included: organic, likely wash, samplers/graders, 7-day totals, top categories, and top buyer wallets. It does not explicitly differentiate from siblings like x402_seller_stats or x402_top_sellers, so it stops short of a 5.

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 or named alternatives appear. The description explains what the summary contains but does not say when an agent should choose it over x402_seller_stats or x402_top_sellers, nor does it state prerequisites beyond the payment cost.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Agent Data API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?