THORChain MCP

Quote Limit Order

quote_limit

Read-onlyIdempotent

Get a limit order quote with expected output, expiry time, and a generated memo for executing the limit order. Limit orders execute when the target price is reached. For an immediate market swap use quote_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>",
      "target_out": "<target_out>"
    },
    "name": "quote_limit"
  }
}

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
`custom_ttl`	No	Custom TTL in blocks for the limit order
`from_asset`	Yes	The source asset (e.g. BTC.BTC)
`target_out`	Yes	The limit price: minimum acceptable output amount in base units (1e8). The order executes only at this price or better
`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)
`refund_address`	No	The refund address if the swap fails
`streaming_quantity`	No	Number of sub-swaps for streaming

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine behavior beyond that: the quote is non-executing by itself, includes an expiry time, and produces a memo the agent needs in order to actually place the limit order. It stops short of describing how long quotes stay valid or any rate limits, so not a 5.

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?

Three short sentences, front-loaded with the core action and return values, followed by the execution semantics and the sibling hand-off. No filler or repetition of the title.

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 ten parameters but full schema documentation and annotations covering the safety profile, the description needs only to frame purpose and the quote-to-memo workflow, which it does. Minor gap: it doesn't say whether the generated memo has an expiry that must be respected or where the memo is used, which matters for a quote-then-execute flow.

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 all ten parameters, including the nuanced target_out limit price and custom_ttl, are already documented in the schema. The description adds no parameter-level detail beyond loosely implying that target_out drives execution and custom_ttl drives expiry. Baseline 3 applies since the schema does the heavy lifting.

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 opens with a specific verb+resource ("Get a limit order quote") and enumerates what comes back: expected output, expiry time, and a generated memo. It explicitly distinguishes itself from the sibling quote_swap, so an agent can route correctly without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the alternative tool (quote_swap) and the condition that selects it ("immediate market swap"), plus states the execution condition for this tool (order fills when target price is reached). When-to-use and when-not-to-use are both covered explicitly.

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?