Skip to main content
Glama

Payment check

verify_payment
Read-onlyIdempotent

Verify an on-chain payment from its transaction hash on Base, Ethereum, Arbitrum, Solana or Bitcoin (chain is detected if omitted). Returns status and verified. pending, unknown and not_found answers are not charged. Free: 1 a day per IP (counted across the HTTP routes and MCP), then $0.003 per call via x402.

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>",
      "expected_amount": "<expected_amount>",
      "receiver": "<receiver>"
    },
    "name": "verify_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoOmit to auto-detect
exactNo
tokenNoSymbol or contract/mint; default USDC (EVM), SOL, BTC
tx_hashYes
receiverYes
not_beforeNo
expected_fromNo
expected_amountYesDecimal string, human units
min_confirmationsNoCan raise, not lower, the chain default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by disclosing the billing model: free tier of 1/day per IP counted across HTTP and MCP routes, then $0.003 via x402, plus the important fact that pending/unknown/not_found responses are not charged. This is exactly the cost/side-effect context an agent needs before calling a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three tight sentences: capability first, then detection/return behavior, then pricing. Every clause carries decision-relevant information with no filler.

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?

For a 9-parameter, paid, multi-chain verification tool with no output schema, it covers chain detection, return fields ('status and verified'), and cost exceptions well. It falls short on matching semantics — what 'exact' toggles, whether partial or overpayment passes, and tolerance behavior — which an agent needs to set expected_amount and exact correctly.

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

Parameters2/5

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

Schema description coverage is only 44%, so the description must compensate, and it largely does not: chain, token defaults and min_confirmations are already documented in the schema, while undescribed parameters like 'exact', 'expected_from' and 'not_before' get no explanation in the description either. The alias mapping lives in the schema, not the description, leaving several semantics undocumented anywhere.

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?

States a specific verb and resource ('Verify an on-chain payment from its transaction hash') and enumerates the five supported chains, which makes the domain unmistakable. Sibling differentiation is only implicit (endpoint_check and scam_check are clearly different domains but never referenced).

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?

Provides useful invocation guidance ('chain is detected if omitted') and cost framing, but never states when to prefer this tool over endpoint_check or scam_check, nor when-not to use it. Usage is implied by the tool's domain rather than stated.

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