xswap.to

Get a swap quote

get_quote

Read-only

Estimate how much the user receives for sending an amount, with the minimum and maximum for the pair. Network fees are already taken out of estimatedAmount. The rate floats, so the result is an estimate, not a promise. Show any warnings to the user.

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": "<amount>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Currency to receive. Currency id from search_currencies, for example btc, eth or usdttrc20.
`from`	Yes	Currency to send. Currency id from search_currencies, for example btc, eth or usdttrc20.
`amount`	Yes	Amount of the from currency, as a decimal like "0.05".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful behavior beyond them: fees are already deducted from estimatedAmount, the rate floats so the value is non-binding, and warnings should be surfaced. That covers the main risk of an agent treating a quote as a guaranteed execution price.

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?

Four short sentences, front-loaded with the core purpose, followed by the caveats that matter (fee treatment, floating rate, warnings). The opening sentence is slightly convoluted ('with the minimum and maximum for the pair'), but no sentence is 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?

There is no output schema, so the description must carry the return-value burden, and it does partially: it names estimatedAmount, min/max, and warnings. It does not sketch the rest of the response shape (e.g., rate or fee fields), which is a modest gap for a read-only quote tool with a fully documented 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 coverage is 100%, so from/to/amount are already fully documented with currency-id examples and decimal formatting. The description adds nothing about the parameters themselves; the 'minimum and maximum for the pair' phrasing describes output, not inputs. Baseline 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: estimates the received amount for a send, including minimum and maximum for the pair. An agent can tell this is a pricing/quote operation rather than a status lookup or a state-changing swap. It does not name or differentiate itself from siblings like create_swap or get_swap_status, which keeps it out of 5 territory.

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 is only implied: as a quote estimator it is naturally the step preceding a swap, and 'Show any warnings to the user' gives post-call handling guidance. There is no explicit statement of when to use this versus create_swap or get_swap_status, and no exclusions or prerequisites.

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

All xswap.to 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?