Skip to main content
Glama

x402_seller_check

Demand check for one Base x402 seller by payTo address, endpoint URL or host: on-chain USDC payers over up to 30 days, how many remain after removing small-funded wallets and market scanners, repeat buyers, USDC received, and how much depends on one wallet. Not charged for unknown or unmeasured sellers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "seller": "<seller>"
    },
    "name": "x402_seller_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
sellerYespayTo address, endpoint URL or host

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the 30-day lookback, the filtering methodology (removes small-funded wallets, market scanners), and a cost behavior (no charge for unknown/unmeasured sellers). It omits read-only confirmation, rate limits, and what an unknown seller returns, keeping it short of a 5.

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?

Front-loaded with the purpose, then a dense but scannable list of outputs, ending with the cost caveat. No filler sentences; the colon-list construction compresses a lot of meaning, though the run-on phrasing takes some parsing.

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?

No output schema exists, so the description must convey return content, and it does list the metrics an agent will get. Combined with the 30-day scope and billing note, an agent has enough to decide and call correctly, though it does not explain result shape or behavior for sellers with no data beyond the no-charge rule.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'seller' parameter is already documented as 'payTo address, endpoint URL or host'; the description restates the same three accepted formats without adding format rules, validation behavior, or ambiguity resolution (e.g., what happens if a host matches multiple sellers). Baseline 3 applies since the schema does the heavy lifting.

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?

States a specific verb+resource: 'Demand check for one Base x402 seller', then enumerates what the check measures (payers over 30 days, filtered counts, repeat buyers, USDC received, concentration). This clearly distinguishes it from discovery siblings like find_x402_endpoints and x402_endpoint_card, though it never names them explicitly.

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 'up to 30 days' scope and the billing note ('Not charged for unknown or unmeasured sellers') imply when the tool is appropriate and give a cost-safety hint, but there is no explicit routing guidance telling an agent when to pick this over x402_endpoint_card or find_x402_endpoints, and no stated prerequisites.

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