Skip to main content
Glama

get_x402_seller_statement

Read-only

Use when an x402 seller or marketplace operator needs an attested on-chain settlement statement for a payee wallet over a bounded period. Ingests Base mainnet USDC Transfer logs, classifies likely x402 settlements, assembles STMT-JCS-1 aggregates and methodology, ML-DSA-65 signs, persists, and anchors the digest. Inputs payee_address (required), period_from and period_to (ISO dates). $3.00 USDC per call.

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": {
      "payee_address": "<payee_address>",
      "period_from": "<period_from>",
      "period_to": "<period_to>"
    },
    "name": "get_x402_seller_statement"
  }
}

Input Schema

NameRequiredDescriptionDefault
period_toYes
period_fromYes
payee_addressYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior2/5

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

The description is genuinely informative about the pipeline (Base USDC Transfer ingestion, x402 classification, STMT-JCS-1 assembly, ML-DSA-65 signing, on-chain digest anchoring) and discloses a $3.00 USDC per-call charge, which annotations do not cover. However, it states that the tool 'persists, and anchors the digest', i.e. it writes stored records and an on-chain anchor, while annotations declare readOnlyHint=true — a direct conflict about whether the environment is modified.

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 sentences, front-loaded with the activation condition, followed by a compact pipeline chain and the cost. The middle sentence is jargon-dense (STMT-JCS-1, ML-DSA-65) but each clause carries distinct information and nothing is repeated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, multi-stage attestation tool with no output schema, the description never says what the caller receives — the signed statement JSON, a storage reference, a transaction hash, or all three — nor how failures (empty period, unanchored statement) surface. The input side and processing chain are covered adequately, but the return contract and the payment/authorization mechanics behind the $3.00 fee are left to inference.

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?

With 0% schema description coverage, the description must carry parameter meaning, and it does partially: it marks payee_address as required and specifies ISO date format for period_from/period_to, which the bare minLength-1 schema does not convey. It still omits address/chain format expectations, timezone semantics, whether the period is inclusive, and any maximum allowed range, so the schema gap is only half closed.

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 and artifact: produce an 'attested on-chain settlement statement' for a payee wallet over a bounded period, and it names the intended caller (x402 seller or marketplace operator). That is far more concrete than the name alone, though it never explicitly contrasts itself with the adjacent get_x402_traffic_diligence tool, so the agent must infer the settlement-vs-diligence split.

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?

'Use when an x402 seller or marketplace operator needs an attested on-chain settlement statement ... over a bounded period' gives clear positive activation criteria tied to role and need. There are no when-not conditions, no mention of what to use instead for raw traffic analysis (e.g. get_x402_traffic_diligence), and no prerequisites such as a funded payer wallet despite the stated fee.

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