Skip to main content
Glama

Quote an XRP swap

quote_swap
Read-only

Live THORChain quote for swapping XRP to BTC, ETH or USDC: expected amount out, every fee (ours is 0.5%), minimum size and expiry. Screens the destination against the OFAC list. Read-only; builds nothing.

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

Input Schema

NameRequiredDescriptionDefault
toYesWhat to receive: BTC (Bitcoin), ETH (Ether) or USDC (USDC on Ethereum).
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

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnlyHint and openWorldHint, yet the description adds real behavioral facts: a 0.5% fee component, a minimum size, quote expiry, and OFAC destination screening. It stops short of saying what happens when the screen rejects an address or how long the quote stays valid, which are the two operational facts an agent would still want.

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?

One dense, front-loaded sentence with a colon-delimited payload list and no filler. The scope and the 'builds nothing' caveat both land before the reader has to hunt for them.

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 usefully enumerates what the quote returns (amount out, all fees, minimum, expiry) and discloses the external dependency (THORChain, OFAC). The residual gap is failure behavior on a screened address and quote lifetime, minor for a read-only quoting tool.

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 every parameter (to, amount_xrp, destination) is already documented with enums and address formats. The description's mention of minimum size adds a little constraint context but does not go beyond the schema's own 'Must be at least the quote's minimum_xrp'. Baseline 3 applies.

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?

States a specific verb and resource (live THORChain quote), the exact pair and destinations supported (XRP to BTC/ETH/USDC), and the returned fields. The clause 'builds nothing' separates it from build_swap_tx without naming it, so an agent can pick correctly from the sibling set.

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?

The phrase 'Read-only; builds nothing' implicitly routes agents here for price discovery first and to build_swap_tx for execution, and the fee/minimum/expiry framing implies pre-trade quoting. It never explicitly names when to prefer swap_status or what to do if the OFAC screen fails, so the guidance is clear but not fully exclusive.

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