Skip to main content
Glama

Build the unsigned XRP Payment

build_swap_tx

Re-quotes and returns ONE unsigned XRP Ledger Payment to THORChain that the caller signs and submits with its own wallet. Same checks as swap.botgraph.org: OFAC screen on both addresses, minimum enforced, memo in MemoData only, no DestinationTag, LastLedgerSequence before the quote expiry. We never sign, submit or hold funds.

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": {
      "from": "<from>",
      "to": "<to>",
      "amount_xrp": "<amount_xrp>",
      "destination": "<destination>"
    },
    "name": "build_swap_tx"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesWhat to receive: BTC (Bitcoin), ETH (Ether) or USDC (USDC on Ethereum).
fromYesThe XRP account (r...) that will sign and pay.
amount_xrpYesXRP to send, e.g. "20" (up to 6 decimals). Must be at least the quote's minimum_xrp.
destinationYesAddress that receives the coins: a Bitcoin address for BTC, an Ethereum 0x address for ETH or USDC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety bar is lower. The description adds real value beyond them: OFAC screening on both addresses, minimum enforcement, memo confined to MemoData, no DestinationTag, LastLedgerSequence bounded by quote expiry, and an explicit "we never sign, submit or hold funds" custody disclaimer.

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 dense sentences, front-loaded with the core action and result, with zero filler. The guarantees list is compact and scannable, though the run-on enumeration of checks is slightly harder to parse than a structured list would be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the burden of explaining the response, yet it only says it returns "ONE unsigned XRP Ledger Payment" and never details the fields the caller needs: transaction blob, quote expiry, minimum_xrp, or what happens on re-quote drift. Coverage of preconditions and custody model is strong, but the return contract is a real gap for a builder tool with no output schema.

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 description coverage is 100%, so the schema already documents all four parameters; baseline is 3. The description only indirectly touches parameters, tying amount_xrp to the quote's minimum_xrp and implying both from/to addresses are OFAC-screened, but adds no format or validation detail the schema lacks.

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?

Uses a specific verb and resource: "Re-quotes and returns ONE unsigned XRP Ledger Payment to THORChain that the caller signs." The verb "re-quotes" implicitly separates it from quote_swap, but the description never names a sibling or states the boundary explicitly, so differentiation is inferred rather than stated.

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?

Usage context is implied: the caller gets an unsigned Payment to sign and submit with its own wallet, and prerequisites such as minimum enforcement and OFAC screening are mentioned. However, there is no explicit when-to-use versus quote_swap or swap_status, and no guidance on whether a prior quote is required before calling.

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