SafeSwapGlobal Crypto Swap Quotes

get_swap_quote

Read-only

Calculates real-time cryptocurrency swap estimates, network fees, deposit limits, and on-chain routing parameters across 240+ multi-chain pairs. Quotes are cached for 30 seconds at the edge. Does not execute transactions or modify state (strictly read-only). Use this tool whenever a user asks to calculate, compare, or estimate an exchange rate between supported cryptocurrencies.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Target cryptocurrency ticker symbol to receive (case-insensitive, e.g. XMR, BTC, USDT, SOL, TON).
`from`	Yes	Source cryptocurrency ticker symbol (case-insensitive, e.g. BTC, XMR, SOL, TON, USDT, ETH, LTC, TRX, DOGE).
`amount`	No	Positive numeric amount of source cryptocurrency to convert. Precision up to 8 decimal places. Rate limits apply per provider pool depth.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`to`	No
`from`	No
`rate`	No
`amount`	No
`provider`	No
`swap_url`	No
`max_amount`	No
`min_amount`	No
`updated_at`	No
`network_fee`	No
`within_limits`	No
`receive_amount`	No
`quote_validity_seconds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 2, 2026

changedInput schema / properties / amount / description

Previous value: -"Amount of source currency to send for conversion. Positive numeric value."New value: +"Positive numeric amount of source cryptocurrency to convert. Precision up to 8 decimal places. Rate limits apply per provider pool depth."

addedInput schema / properties / amount / minimum
```
Added value: +1e-8
```

changedInput schema / properties / from / description

Previous value: -"Source cryptocurrency ticker symbol. Must be a valid supported asset ticker such as BTC, XMR, SOL, TON, USDT, or ETH."New value: +"Source cryptocurrency ticker symbol (case-insensitive, e.g. BTC, XMR, SOL, TON, USDT, ETH, LTC, TRX, DOGE)."

changedInput schema / properties / to / description

Previous value: -"Target cryptocurrency ticker symbol that user wants to receive, such as XMR, BTC, USDT, or SOL."New value: +"Target cryptocurrency ticker symbol to receive (case-insensitive, e.g. XMR, BTC, USDT, SOL, TON)."

addedOutput schema / properties / quote_validity_seconds
```
Added value: +{
+  "type": "number"
+}
```

First observedOct 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, but the description adds real behavioral value by disclosing the 30-second edge cache (freshness expectations) and the breadth of returned data (fees, limits, routing). It stops short of describing rate limits or failure modes beyond the vague per-provider note in the schema.

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 tight sentences: what it computes, the caching constraint, the safety profile, then a usage trigger. Everything is front-loaded and every sentence earns its place with no repetition of schema fields.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is not required, and the description still previews the result contents (fees, deposit limits, routing). Combined with the read-only disclosure and caching note, an agent has everything needed to call it correctly.

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 'from', 'to' and 'amount' fully documented including examples, defaults, minimum and precision, so the schema carries the parameter burden. The description adds only indirect context ('240+ multi-chain pairs') and no syntax or format guidance beyond it — the baseline 3 is correct.

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 names a specific verb ('Calculates') and concrete resources (swap estimates, network fees, deposit limits, routing parameters) plus the scope (240+ multi-chain pairs). An agent can distinguish this from the only sibling, list_supported_currencies, because this one returns quotable rates rather than a currency catalog.

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?

'Use this tool whenever a user asks to calculate, compare, or estimate an exchange rate between supported cryptocurrencies' gives an explicit triggering condition. It also implicitly excludes execution ('Does not execute transactions'), but never names an alternative tool or states when a different quote source should be preferred.

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

All SafeSwapGlobal Crypto Swap Quotes 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?