Skip to main content
Glama

Stratalize Intelligence

Get X402 Seller Statement

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

A3.5/5.0
Behavior2/5

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

The description adds substantial context beyond the annotations — the data source (Base mainnet USDC Transfer logs), the cryptographic scheme (ML-DSA-65), persistence, digest anchoring, and a $3.00 per-call fee. But 'persists, and anchors the digest' describes state-changing side effects, which conflicts with the declared readOnlyHint=true. That conflict undercuts the main behavioral signal an agent needs.

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?

Two sentences, front-loaded with the usage trigger, then the mechanics, then inputs and price — no filler. The middle clause is dense with jargon (STMT-JCS-1) but each element carries information.

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 explain what comes back at a high level (a signed, persisted, anchored statement) and discloses cost, which is the key call-time consideration. What the statement actually contains and whether a returned digest is verifiable are left implicit, but overall it is sufficient to invoke correctly.

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 0%, so the description carries the full burden; it does name all three parameters, marks payee_address required, and specifies ISO dates for the period bounds, which meaningfully beats the bare 'string' schema. It does not describe the address format/chain expectations or whether periods are inclusive, so a meaningful gap remains.

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 names a specific verb-and-resource pair — producing an attested on-chain settlement statement for a payee wallet over a bounded period — and spells out the pipeline (USDC Transfer logs, x402 classification, STMT-JCS-1 aggregates, ML-DSA-65 signing, anchoring). It does not, however, distinguish itself from the closest sibling, get_x402_traffic_diligence, so an agent must infer the boundary.

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 leading 'Use when an x402 seller or marketplace operator needs...' clause gives a clear trigger audience and condition, which is stronger than most. It stops short of stating exclusions or naming an alternative (e.g., when to prefer the traffic-diligence sibling), so routing among x402 tools is still partly guesswork.

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