THORChain MCP

Quote Swap

quote_swap

Read-onlyIdempotent

Calculate how much output you would receive when swapping one asset for another. Use this tool to answer questions like 'how much ETH would I get for 100 RUNE?' Returns expected output amount, fees, slippage, estimated time, and a memo for executing the swap.

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_asset": "<from_asset>",
      "to_asset": "<to_asset>",
      "amount": "<amount>"
    },
    "name": "quote_swap"
  }
}

Input Schema

Name	Required	Description
`amount`	Yes	The amount in base units (1e8 for most assets)
`to_asset`	Yes	The target asset (e.g. ETH.ETH)
`affiliate`	No	The affiliate address or THORName
`from_asset`	Yes	The source asset (e.g. BTC.BTC)
`destination`	No	The destination address for the swap output
`affiliate_bps`	No	The affiliate fee in basis points (0-1000; protocol caps total affiliate fees at 1000 bps)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real value beyond that by enumerating the return payload (output amount, fees, slippage, estimated time, memo) and by noting the memo is for executing the swap, implying a follow-up action. It does not say whether the quote expires or is a firm commitment, which is the notable 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.

Conciseness5/5

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

Two sentences, front-loaded with the core action and followed by a use-case example and a return summary. Every sentence carries information and 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?

With no output schema, the description usefully compensates by listing the fields returned, and the annotations cover the read-only nature. For a quoting tool it omits quote validity/expiry semantics and any indication of how fresh the estimate is, which an agent answering a user's swap question would want.

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%, with each of the six parameters documented, including base-unit conventions for amount and the 1000 bps affiliate cap. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 ('Calculate how much output you would receive when swapping one asset for another') and reinforces it with a concrete example question. It never names a sibling, so an agent must infer on its own why this differs from prepare_swap or quote_limit.

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 clear context for use ('Use this tool to answer questions like how much ETH would I get for 100 RUNE?'), which squarely frames it as a read-only estimation step. It stops short of stating exclusions or pointing to alternatives such as prepare_swap for actually executing, so the boundary with siblings is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All THORChain MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?