Skip to main content
Glama

Read a payment response on its chain

check_payment_proof
Read-onlyIdempotent

check_payment_proof reads a seller PAYMENT-RESPONSE header, or a network and a transaction hash, on a chain vet402 reads again after a purchase. It returns whether the transaction is on that chain, plus from, to, asset and amount in atomic units. A chain outside that set comes back as unsupported_network. vet402 does not pay and does not sign.

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": "check_payment_proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoChain id, such as eip155:8453, or a name such as base. Pass it with transaction when payment_response is left out.
transactionNoTransaction hash on that chain. Pass it with network when payment_response is left out.
payment_responseNoSeller PAYMENT-RESPONSE header as base64 JSON with transaction and network.

Output Schema

NameRequiredDescriptionDefault
toYes
txYes
fromYes
as_ofYes
assetYes
blockYes
foundYes
amountYes
statusYes
networkYes
explorerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the bar is lower. The description still adds real behavioral context: the unsupported_network outcome for chains outside the accepted set, that amounts come back in atomic units, and the safety statement that vet402 does not pay and does not sign.

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 tightly packed sentences: purpose and scope first, then the return payload, then the error case and the no-signing guarantee. Nothing is redundant, though the phrase 'on a chain vet402 reads again after a purchase' is slightly indirect.

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?

An output schema exists, so return values need not be spelled out, yet the description names the key fields anyway. Combined with the error-case behavior and the no-pay/no-sign guarantee, an agent has what it needs to call this correctly; only explicit sibling routing is absent.

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 coverage is 100% and each parameter already documents itself, including the mutually exclusive payment_response vs network+transaction paths. The description reinforces the alternative modes and clarifies atomic units for amounts but adds no syntax or format meaning 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?

The description states a specific verb and resource ('reads a seller PAYMENT-RESPONSE header, or a network and a transaction hash') and narrows scope to a chain vet402 reads. It also names what is returned (on-chain status, from, to, asset, amount in atomic units), which is enough to distinguish it from seller-lookup siblings like check_x402_seller or find_x402_sellers.

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?

It conveys the situation where this applies ('on a chain vet402 reads again after a purchase') and describes two alternative invocation paths, but never explicitly says when to prefer it over check_x402_seller or check_my_x402_endpoint, nor any when-not conditions.

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.