Skip to main content
Glama

Payment verify

payment_verify
Read-onlyIdempotent

Payment verification across 8 EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Arc and Robinhood): did a transaction really pay an address, totals per token, whether a minimum was met, confirmations. $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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>",
      "to": "<to>"
    },
    "name": "payment_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesaddress that should have been paid
minNominimum in token units
hashYestransaction hash (0x + 64 hex)
chainNoethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood
tokenNocount only this token (0x...)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / description
      Previous value: -"ethereum (default), base, arc or bnb"New value: +"ethereum (default), base, arbitrum, optimism, polygon, bnb, arc or robinhood"
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the bar is lower, and the description still adds substantive context: the price ($0.001/call), the accepted payment rails (USDC on Arc/Base/Solana, XNT on X1), and that a payment-less call returns terms rather than erroring. It stops short of explaining settlement failure behavior or whether the paid call is repeatable without a new payment, despite idempotentHint=true.

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-loaded with the outcome and the supported chains, then pricing, then the payment handshake. Dense but every clause carries information; the long parenthetical chain list is verbose but justified because the chain parameter has no enum in the schema.

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 describing the result shape (paid-or-not, per-token totals, minimum check, confirmations). With all six parameters documented and the payment/pricing model spelled out, an agent has what it needs to invoke this correctly.

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 coverage is 100%, so baseline is 3, but the description adds real value beyond it: it explains the two-phase use of `payment` (first call returns terms to sign, second call passes the signed payload) and enumerates the valid `chain` values, which the schema leaves as a free string with no enum.

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 ('Payment verification') and enumerates exactly what is determined: whether a transaction paid an address, per-token totals, minimum-threshold satisfaction, and confirmations. The chain list and the distinction from a raw transaction lookup (evm_tx) are implicit in the outcome-oriented framing, so an agent can tell what it gets 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?

Gives an explicit operational sequence: call once without `payment` to obtain terms, sign with your own wallet, call again with `payment` to complete the purchase. That is clear usage context, but it does not name when to prefer this over siblings such as evm_tx or tx_batch_status, nor any exclusions.

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