x402-data-gateway

Verify Base USDC Settlement

settlement_proof

Verify one claimed canonical Base USDC settlement after execution by matching a successful transaction receipt to the exact recipient, atomic amount, and optional payer. Use payment_offer_preflight before authorization when you need to inspect an unpaid x402 or MPP offer instead. This tool reads only public Base receipt and log data; it reads no merchant ledger and performs no wallet, signing, broadcast, custody, or execution action.

Input Schema

TableJSON Schema

Name	Required	Description
`payer`	No	Optional expected canonical Base USDC payer.
`recipient`	Yes	Expected canonical Base USDC recipient.
`amountAtomic`	Yes	Expected positive USDC amount in six-decimal atomic units.
`transactionHash`	Yes	Base mainnet transaction hash containing the claimed canonical USDC transfer.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`asset`	Yes
`chain`	Yes
`product`	Yes
`request`	Yes
`version`	Yes
`boundary`	Yes
`decision`	Yes
`findings`	Yes
`checkedAt`	Yes
`settlement`	Yes
`transaction`	Yes

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It explicitly states the tool 'reads only public Base receipt and log data' and 'performs no wallet, signing, broadcast, custody, or execution action,' which is strong transparency for a verification tool.

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?

Three sentences, each earning its place: purpose and matching criteria, alternative tool guidance, and safety/read-only behavior. The description is front-loaded and free of filler.

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

Completeness5/5

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

Given the tool's moderate complexity, the presence of an output schema, and 100% schema parameter coverage, the description sufficiently covers purpose, usage context, behavioral constraints, and parameter intent. No critical context is missing.

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 description coverage is 100%, so the baseline is 3. The description adds the notion of 'exact' matching and 'optional payer,' but it does not materially enrich parameter semantics beyond the schema's own 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 uses a specific verb ('Verify') with a precise resource ('claimed canonical Base USDC settlement') and defines the matching criteria (successful transaction receipt, exact recipient, atomic amount, optional payer). This clearly differentiates it from generic receipt tools like transaction_receipt and from preflight tools like payment_offer_preflight.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool ('after execution') and names a specific alternative for a different scenario: 'Use payment_offer_preflight before authorization when you need to inspect an unpaid x402 or MPP offer instead.' This gives clear contextual guidance.

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

All x402-data-gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation3/5

Several tools cluster around the same domain: there are multiple audit tools, multiple preflight tools, multiple receipt/settlement tools, and two wallet-policy-conformance tools. The descriptions are carefully distinguished with 'use X instead' notes, but an agent would still need to read closely to separate `agent_discoverability_audit` from `agent_surface_budget_audit` and `seller_integrity_audit` from `payment_offer_preflight`.

Naming Consistency4/5

Most names follow a readable, snake_case pattern with a domain prefix or action stem, such as `morpho_position`, `transaction_receipt`, `wallet_enrich`, and `contract_qualified_search`. The convention is not fully uniform—`read`, `extract`, `scan`, and `schemaforge` are standalone verbs or compounds, and `agent_surface_budget_audit` is a much longer construction—but the style is consistent enough to navigate.

Tool Count3/5

22 tools is at the heavy end of a data-gateway scope, especially since they spread across x402 discovery, Morpho lending, web domain audits, wallet policy, and blockchain receipts. Each tool explains its existence, but the set feels broader than one central data-gateway concern.

Completeness4/5

The tools form a coherent read-only x402/agent-commerce lifecycle: catalog search, discoverability, surface/seller integrity, payment offer preflight, settlement proof, and transaction receipt verification. There are some peripheral tools that do not directly serve x402, and no payment or execution action exists, but the read-only audit gate is intentionally complete and lacks dead ends.

Verify Base USDC Settlement

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources