Skip to main content
Glama

x420_chain_proof-of-payment

Verify a Base mainnet transaction hash as a token payment by checking receipt status, confirmations, ERC-20 transfers, recipient, and minimum amount against expected values.

Instructions

Base proof of payment: Verifies a Base mainnet transaction hash as a token payment: receipt status, block time, confirmations, every ERC-20 Transfer it emitted for the token (USDC by default), and pass/fail checks against an expected recipient and minimum amount. Source: Base mainnet RPC. Not a settlement guarantee. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.10 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: status, block, block_time, confirmations, transfers[{from, to, amount}], checks{}, verified - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"tx_hash":"0x9f2c6c1e7b3a4d5e8f90a1b2c3d4e5f60718293a4b5c6d7e8f9012345678abcd","expected_to":"0x7C2E8c5D2F1bc1f0Cc6B7e3E4C2a1b9D8e7F6A5B","expected_amount":"0.10"}.

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": {
      "tx_hash": "<tx_hash>"
    },
    "name": "x420_chain_proof-of-payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoERC-20 contract to inspect (default USDC on Base)
tx_hashYes0x transaction hash
expected_toNorecipient address the payment must have reached (default: any)
expected_amountNominimum token amount, e.g. 0.10 (default: any)
min_confirmationsNoconfirmations required (default 1)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond annotations by disclosing that the call costs $0.10 USDC per invocation, is settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY, and involves real money — critical context for an agent deciding whether to retry. It also names the data source (Base mainnet RPC), sets expectations ('Not a settlement guarantee'), and describes the deliverable including a signed receipt and settlement transaction.

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-loads what the tool verifies, then source, caveats, price, return shape, and an example — a sensible descending-priority order. The generic legal disclaimer sentence adds length without operational value, but the rest is dense and information-bearing.

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?

For a paid verification call with no output schema, the description covers source, cost and payment path, what is returned (status, block, block_time, confirmations, transfers, checks, verified), defaults, and a sample invocation. The only omission is error behavior for pending or reverted transactions, which is minor against the rest.

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

Parameters4/5

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

Schema description coverage is already 100%, so baseline is 3; the description adds meaning by framing expected_to and expected_amount as pass/fail check inputs and confirms token defaults to USDC. The example input demonstrates concrete string formats for tx_hash and the decimal amount ('0.10'), which the schema alone does not show.

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 ('Verifies a Base mainnet transaction hash as a token payment') and enumerates exactly what is checked: receipt status, block time, confirmations, emitted ERC-20 Transfers, and pass/fail checks vs expected recipient and minimum amount. An agent can distinguish this from siblings like x420_chain_wallet-balance or x420_chain_token-metadata without opening the schema.

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?

Clear context for when to call it: confirming that an on-chain transaction actually paid a given recipient at least a given amount, with token defaulting to USDC. It does not name alternatives or state when-not to use it (e.g., pre-broadcast or pending transactions), so routing guidance is implied rather than explicit.

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