Skip to main content
Glama

Create Payment Invoice

get_invoice

Request a payment invoice for any SqueezeOS endpoint. Returns destination address, amount, and payment_options for XRPL (RLUSD or USDC), Xahau (native XAH), Base (USDC), or Solana (USDC-SPL). Pass currency='USDC' and chain='solana' for Solana; pass asset='XAH' (or chain='xahau') for the Xahau rail. Xahau invoices for third-party endpoints also return fee_required/fee_amount/fee_pay_to/fee_memo_hex: a flat 0.01 XAH facilitator fee paid as a second Xahau Payment (SML endpoints are fee-exempt; XRPL invoices for third-party endpoints likewise bind a flat 0.01 facilitator fee in the invoice's asset, from the first settlement). 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": {
      "endpoint_id": "<endpoint_id>"
    },
    "name": "get_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoRLUSD (default, XRPL), USDC (XRPL/Base/Solana per chain), or XAH (Xahau)
chainNosolana — use Solana USDC-SPL rail; base — use Base USDC rail; xrpl — use USDC on XRPL; xahau — use Xahau native-XAH rail
currencyNoUSDC for Base/Solana rail; omit for RLUSD on XRPL
endpoint_idYesUUID of endpoint to pay for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations mark this as non-read-only and non-idempotent, and the description supplies substantial context beyond them: it lists returned fields despite no output schema, and explains the flat 0.01 XAH facilitator fee, the second Xahau Payment, fee_memo_hex, and which endpoints are fee-exempt. The notable gap is that it never says whether repeat calls produce distinct invoices or how long an invoice stays valid — relevant given idempotentHint=false.

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 purpose and return shape, then rail selection, then fee mechanics — a sensible ordering with no filler sentences. The fee sentence is dense and packs four distinct facts (fee amount, payment mechanism, SML exemption, XRPL analogue) into one long clause, which costs a little readability but each detail is load-bearing.

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?

With no output schema, the description correctly compensates by naming the returned fields and by documenting fee fields that appear only for third-party Xahau endpoints, which is exactly the kind of conditional return behavior an agent needs. Remaining gaps are invoice lifecycle concerns (expiry, re-request semantics) rather than anything required to make a correct call.

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 the baseline would be 3, but the description genuinely adds meaning the schema does not: it explains the working combinations (currency='USDC' with chain='solana', asset='XAH' equivalent to chain='xahau') and that RLUSD is the default XRPL asset. This helps an agent avoid malformed rail combinations rather than just restating each field.

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 action and resource ("Request a payment invoice for any SqueezeOS endpoint") and enumerates what comes back (destination address, amount, payment_options). The title "Create Payment Invoice" and the name get_invoice are reconciled by the phrase "Request a payment invoice," so there is no confusion about it being a mutating creation step. It does not explicitly name a sibling it replaces (e.g., verify_payment), which keeps it from a 5.

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 concrete routing guidance: currency='USDC' plus chain='solana' for Solana, asset='XAH' or chain='xahau' for Xahau, and notes the call is free. It also states when the extra facilitator fee applies (third-party endpoints) versus when it does not (SML endpoints, fee-exempt). It stops short of saying when to prefer this over verify_payment or when an invoice should be regenerated, so no explicit exclusions or alternatives.

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