Skip to main content
Glama

Verify Payment & Issue Access Token

verify_payment
Idempotent

Submit tx_hash after paying an invoice. Supports XRPL, Xahau, Base (0x… hash), and Solana. Returns a signed JWT access_token (1-hour TTL). For a Xahau invoice with fee_required=true, also submit fee_tx_hash (the 0.01 XAH facilitator-fee payment) — settlement requires both payments. 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": {
      "invoice_id": "<invoice_id>",
      "recovery_secret": "<recovery_secret>",
      "tx_hash": "<tx_hash>",
      "agent_wallet": "<agent_wallet>"
    },
    "name": "verify_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
tx_hashYesXRPL/Xahau: 64-char hex; Base: 0x-prefixed hex; Solana: base58 signature
invoice_idYesInvoice ID returned by get_invoice
fee_tx_hashNoXahau only, when the invoice has fee_required=true: tx hash of the 0.01 XAH facilitator-fee payment to fee_pay_to carrying fee_memo_hex
agent_domainNoOptional domain of the paying agent, recorded on the compliance receipt
agent_walletYesThe paying agent's wallet address on the invoice's rail (XRPL classic address, Base 0x address, or Solana address)
recovery_secretYesPrivate high-entropy secret returned only with the original invoice; required to recover a previously settled token after lost response/restart

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / agent_domain / description
      Added value: +"Optional domain of the paying agent, recorded on the compliance receipt"
    • addedInput schema / properties / agent_wallet / description
      Added value: +"The paying agent's wallet address on the invoice's rail (XRPL classic address, Base 0x address, or Solana address)"
    • addedInput schema / properties / invoice_id / description
      Added value: +"Invoice ID returned by get_invoice"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (idempotent, open-world, non-destructive), the description discloses the return artifact and its 1-hour TTL, the dual-payment settlement rule on Xahau, and that the call is free. It does not explain failure modes or what happens on an invalid or already-consumed hash, which is the main remaining gap.

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 front-loaded sentences carrying the action, supported rails, return value, and conditional fee requirement. The trailing 'Free.' fragment is terse but informative; there is 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 state-changing tool with no output schema, the description covers the return value, TTL, per-rail input expectations, and the extra payment case. Error behavior and the role of the JWT downstream are left implicit, but nothing needed to invoke it correctly is missing.

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 already 100%, but the description adds real meaning on top: per-rail tx_hash formats and, most importantly, the conditional rule that fee_tx_hash is required only when fee_required=true. It adds nothing about recovery_secret beyond what the schema says.

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 action (submit a tx_hash) and outcome (returns a signed JWT access_token), and it names the exact rails it accepts (XRPL, Xahau, Base, Solana). This clearly separates it from read-oriented siblings like get_invoice or get_compliance_receipt.

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 condition: call after paying an invoice, submitting tx_hash, plus a conditional branch for Xahau fee_required invoices needing fee_tx_hash. It doesn't name alternative tools or state what to do when verification fails, but the preconditions are explicit.

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