Skip to main content
Glama

top_x402_sellers

Rank the top x402 sellers on Base by USDC earned or call count in the last 24 hours, using on-chain transfer data. Discover active sellers and where to direct demand.

Instructions

List the x402 sellers earning the most USDC (or serving the most calls) on Base in the last ~24h, derived from on-chain USDC transfers. Useful for agents discovering the live x402 economy: who's getting paid, which networks, and where to point demand. Free to call (no payment, no proof-of-work). Defaults: top 10, sort by USDC, exclude this service's own wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoRank by USDC settled (default) or by call count
limitNoMax rows to return (default 10, max 50)
includeNo'external' (default) hides this service's own wallet; 'all' includes it
Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses default behavior (top 10, sort by USDC, exclude own wallet) and that the data is derived from on-chain USDC transfers and is free. It lacks details on rate limits or data freshness beyond 'last ~24h', but overall provides sufficient transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, front-loaded with the core purpose, followed by usefulness and defaults. Every sentence adds value with no redundancy or fluff.

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?

Given no output schema and no annotations, the description covers the tool's purpose, usage, and defaults adequately. It could be improved by briefly noting the output format (e.g., list of sellers with metrics), but the current description is sufficient for a simple listing 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 schema covers all parameters (100% coverage), so baseline is 3. The description adds value by explaining defaults (limit default 10, max 50) and the 'include' parameter's effect (exclude own wallet by default), going beyond the schema descriptions.

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 clearly states the tool lists x402 sellers earning most USDC or serving most calls on Base in the last ~24h, with specific verb 'list' and resource 'x402 sellers'. It distinguishes itself from sibling tools by focusing on a niche on-chain economy.

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

Usage Guidelines4/5

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

The description explains it is useful for discovering the live x402 economy and notes it is free to call with no payment or proof-of-work required. However, it does not explicitly exclude misuse cases or describe when to prefer alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MikeyPetrillo/Agent402'

If you have feedback or need assistance with the MCP directory API, please join our Discord server