Skip to main content
Glama

USDC payment receipt

payment_receipt
Read-only

Use when you need a signed observation of an existing Base USDC transfer. Verify a native Base USDC transfer by tx_hash (optional log_index), or exact pay_to + decimal amount + past start/end (max 90 days). Ambiguous matches fail without charge. Signed observation, OFAC flags, confirmations and printable HTML. Not invoice ownership or finality proof. Price $0.01 USDC on Base. No free trial. Price: 0.01 USDC. Minimal input example: {"tx_hash":"0x9ede68ce1d33fd5d49d402d11de3127710102235ac5bdf020344345dfeb8ce4f"}. Illustrative output excerpt: {"result":{"kind":"payment_receipt","receipt":{"amount":"0.050000","time":"2026-10-22T22:07:07.000Z"}},"jws":"illustrative-not-a-live-signature"}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): No shared free trial for this tool. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payment_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoOptional. Exclusive past end timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-02T00:00:00Z. Must be later than start and not in the future. Required in matching mode when tx_hash is absent.
startNoOptional. Inclusive past start timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-01T00:00:00Z. Start/end window must be at most 90 days. Required in matching mode when tx_hash is absent.
amountNoOptional. Exact native Base USDC amount as a decimal string with at most six fractional digits. Example: "1.25" (1250000 atomic units). Required with pay_to, start and end when tx_hash is absent.
pay_toNoOptional. 0x-prefixed 20-byte recipient Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58. Required with amount, start and end when tx_hash is absent.
tx_hashNoOptional. 0x-prefixed 32-byte Base transaction hash string. Example format: 0x1111111111111111111111111111111111111111111111111111111111111111. Supply a real hash, optionally with log_index; otherwise supply pay_to, amount, start and end. Do not combine the two lookup modes.
log_indexNoOptional. Nonnegative transaction log index integer, at most 1000000. Example: 0. Optional only with tx_hash; use to disambiguate transfers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / amount / description
      Added value: +"Optional. Exact native Base USDC amount as a decimal string with at most six fractional digits. Example: \"1.25\" (1250000 atomic units). Required with pay_to, start and end when tx_hash is absent."
    • addedInput schema / properties / end / description
      Added value: +"Optional. Exclusive past end timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-02T00:00:00Z. Must be later than start and not in the future. Required in matching mode when tx_hash is absent."
    • addedInput schema / properties / log_index / description
      Added value: +"Optional. Nonnegative transaction log index integer, at most 1000000. Example: 0. Optional only with tx_hash; use to disambiguate transfers."
    • addedInput schema / properties / pay_to / description
      Added value: +"Optional. 0x-prefixed 20-byte recipient Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58. Required with amount, start and end when tx_hash is absent."
    • addedInput schema / properties / start / description
      Added value: +"Optional. Inclusive past start timestamp string in ISO 8601 with timezone; UTC recommended. Example: 2026-10-01T00:00:00Z. Start/end window must be at most 90 days. Required in matching mode when tx_hash is absent."
    • addedInput schema / properties / tx_hash / description
      Added value: +"Optional. 0x-prefixed 32-byte Base transaction hash string. Example format: 0x1111111111111111111111111111111111111111111111111111111111111111. Supply a real hash, optionally with log_index; otherwise supply pay_to, amount, start and end. Do not combine the two lookup modes."
  2. Changed1 schema field changed
    • changedInput schema / description
      Previous value: -"Example arguments: {\"tx_hash\":\"0x1111111111111111111111111111111111111111111111111111111111111111\"}"New value: +"Example arguments: {\"tx_hash\":\"0x9ede68ce1d33fd5d49d402d11de3127710102235ac5bdf020344345dfeb8ce4f\"}"
  3. Added

TDQS

A4/5.0
Behavior5/5

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

The annotations already establish that the tool reads data and does not destroy anything, but the description adds much more: ambiguous matches fail without charge, confirmations and OFAC flags are returned, printable HTML is produced, the price is $0.01 USDC with no free trial, and the x402 payment continuation requires explicit wallet approval. It also says what to do when a signed attempt has an unknown outcome and forbids silent fallback to payment, which is exactly the operational context 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.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded well, but it wastes space badly: the price is stated three times ('Price $0.01 USDC on Base', 'No free trial', 'Price: 0.01 USDC'), the illustrative output excerpt appears twice plus a disclaimer, and the payment narrative runs many sentences. Much of that belongs in a payment-handling guide rather than in the tool contract.

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?

There is no output schema, so the description carries the burden of showing the return shape, and it does provide an illustrative receipt excerpt with amount and time plus the jws field. It also covers pricing, failure behavior, and the payment protocol requirement. What it lacks is detail on what the confirmation count and OFAC flag actually mean, and how the receipt is consumed downstream.

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?

The schema description coverage is already 100%, but the description still adds value by explaining how parameters combine: it offers either tx_hash plus an optional log_index, or the exact triple of pay_to, decimal amount, and a past window capped at 90 days. It also warns that ambiguous matches fail. The rest of the parameter detail is duplicated from the schema, which holds the score below 5.

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: verify a native Base USDC transfer and return a signed observation. It also states scope limits ('Not invoice ownership or finality proof') and describes two distinct lookup modes. It does not name which sibling would be the right choice for a related need, so it falls short of a 5.

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?

It gives a clear trigger ('Use when you need a signed observation of an existing Base USDC transfer'), spells out two alternative lookup paths, and states that the two modes must not be combined. However, it never names a sibling tool as an alternative for either the pre-payment check or the wallet-history case, so the agent has to infer the boundary itself.

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.