Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Payment receipt for an x402 or USDC payment from its transaction hash

x402_receipt
Read-only

Turn a settled x402 or USDC payment into a receipt to file: from the transaction hash, the payer, payee, amount, time, block, status and whether it was an EIP-3009 authorization (the x402 exact scheme), on Base, Ethereum, Arbitrum, Optimism or Polygon, with a stable receipt id and a SHA-256 of a canonical text for bookkeeping. Optionally name what was bought. Never signs. Use to keep proof of a purchase after an agent pays. Example: hash=0x778c8c1b1fd1b320bf045eae0af7274e74a9e2e1f83c34ec96d9f825aea3b933. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "hash": "<hash>"
    },
    "name": "x402_receipt"
  }
}

Input Schema

NameRequiredDescriptionDefault
hashYesTransaction hash of the payment (0x, 64 hex characters)
chainNoNetwork: base (default), eth, arb, op or polygon
payToNoOptional: the payee, when the transaction holds several USDC transfers
resourceNoOptional: the URL or item the payment bought, written into the receipt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations it discloses several things an agent could not infer: it never signs, it only reads/computes and changes nothing, and each call is billed ($0.01 via x402 USDC or card key, first 25 free, failed calls free) so repeats are not free. The charging note is consistent with idempotentHint=false and is exactly the kind of cost/behavioral disclosure that matters before invoking a paid tool.

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?

The core action and inputs are front-loaded, and the trailing pricing/safety notes earn their place because they affect whether an agent calls it. The main sentence is a long dense clause chain, but there is no filler or repetition.

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?

There is no output schema, and the description compensates by enumerating the receipt fields returned, the supported chains, the optional annotations that get written into the receipt, and the billing model. An agent has enough to decide to call it and to interpret the result.

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 all four parameters are already documented in the schema, and the description adds little beyond it ("optionally name what was bought" restates `resource`; the chain list restates the `chain` enum). The sample hash value is mildly useful but does not deepen parameter meaning, so the baseline 3 applies.

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: turning a settled x402/USDC payment into a receipt from a transaction hash, and enumerates the fields produced (payer, payee, amount, block, status, EIP-3009 flag, receipt id, SHA-256). It is clear what the tool does, but it never explicitly distinguishes itself from the chain-specific siblings (base_receipt, arb_receipt, eth_receipt, op_receipt, polygon_receipt) despite overlapping with them via the `chain` parameter.

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?

"Use to keep proof of a purchase after an agent pays" gives a clear situational trigger, and the example hash shows the intended call shape. There is no explicit when-not guidance and no mention of when a chain-specific receipt sibling would be preferable, so it stops short of full routing guidance.

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.