Skip to main content
Glama

MoneyTools payment-safety suite

Verify a USDC settlement

x402_verify_settlement
Read-onlyIdempotent

Verify an on-chain USDC settlement: tx hash on network (base, base-sepolia, polygon, arbitrum, avalanche, bsc) paid amount to payTo. Returns verdict valid|invalid|pending|not_found. Free to try: 20 MCP calls/day per client, no API key or wallet needed (beyond that: prepaid credits via header X-API-Key, see server instructions).

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": {
      "txHash": "<txHash>",
      "payTo": "<payTo>",
      "amount": "<amount>"
    },
    "name": "x402_verify_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoexpected payer 0x address (optional)
matchNoexact (default) or atLeast
payToYesexpected recipient 0x address
amountYesdecimal USDC, e.g. 0.01
txHashYes0x transaction hash (66 chars)
networkNobase | base-sepolia | polygon | arbitrum | avalanche | bscbase
minConfirmationsNodefault 2

Output Schema

NameRequiredDescriptionDefault
validNo
reasonsNo
verdictYes
confirmationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior, so the bar is lower, but the description adds real operational context: a 20 calls/day per-client free quota, no API key or wallet required within that quota, and paid credits via X-API-Key beyond it. It also names the verdict vocabulary, though that partly duplicates the output schema.

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 compact sentences/fragments with the core action front-loaded and the access/quota caveat trailing in parentheses. Nothing is padded, though the nested parenthetical about credits is slightly dense for the value it carries.

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?

For a 7-parameter, 3-required verification tool with an output schema, the definition covers the action, the verdict set, and the auth/quota model, which is what an agent needs to call it. It does not explain confirmation semantics or pending-state resolution, but those are largely delegated to the schema and output schema.

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 every parameter is already documented with meaning, defaults, and the enum for match. The description only restates the network list and the payTo/amount relationship, and adds no syntax or edge-case guidance (e.g., how match=atLeast interacts with amount) beyond the schema.

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?

States a specific verb and resource ('Verify an on-chain USDC settlement') plus the exact inputs that define the check (tx hash, network, paid amount, payTo). That distinguishes it from sibling verification tools like x402_precheck or x402_validate, which do not settle on-chain.

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 phrase 'Verify an on-chain USDC settlement' implies the use case, and the free-tier/auth note tells the agent about access conditions. However, there is no explicit guidance on when to prefer this over the many x402 siblings (precheck, validate, find_endpoint), nor any when-not guidance, so routing is left partly to inference.

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