Skip to main content
Glama
Sign In

Cambio

by one.cambio
OverviewDiscussionsAdmin

Get a Cambio swap quote

get_quote
Read-onlyIdempotent

Cambio’s quote for swapping one crypto asset to another, for an exact amount sent or an exact amount to receive, with how it compares to other exchanges. For someone who wants to swap, convert or exchange crypto, asks how much they would receive, or asks how much they need to send to get an amount. Each leg takes its network (for example tron, bsc, ethereum, arbitrum, solana, bitcoin). The card shows every amount. The swap itself is created on cambio.one or in Telegram from the card’s buttons, never here.

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_currency": "<from_currency>",
      "to_currency": "<to_currency>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoAmount of from_currency the customer sends, as the customer wrote it, e.g. "10". Empty when the customer named the amount to receive instead.
to_networkNoNetwork the customer receives on, as the customer named it. Empty when the customer did not name one, with the same result as from_network.
to_currencyYesAsset the customer receives
from_networkNoNetwork of the asset sent, as the customer named it, e.g. tron, bsc, ethereum, arbitrum, solana, bitcoin. Empty when the customer did not name one: a coin Cambio offers on one network only gets it filled in, and for any other the result lists the networks Cambio offers it on.
from_currencyYesAsset the customer sends, e.g. USDT, BTC, ETH
receive_amountNoAmount of to_currency the customer wants to receive, as the customer wrote it, e.g. "500" in "I need 500 USDT on Tron, paying with ETH". Empty when the customer named the amount sent. The quote then says how much from_currency is sent to receive it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount of from_currency the customer sends, as the customer wrote it, e.g. \"10\""New value: +"Amount of from_currency the customer sends, as the customer wrote it, e.g. \"10\". Empty when the customer named the amount to receive instead."
    • addedInput schema / properties / receive_amount
      Added value: +{
+  "description": "Amount of to_currency the customer wants to receive, as the customer wrote it, e.g. \"500\" in \"I need 500 USDT on Tron, paying with ETH\". Empty when the customer named the amount sent. The quote then says how much from_currency is sent to receive it.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "from_currency",
-  "to_currency",
-  "amount"
-]New value: +[
+  "from_currency",
+  "to_currency"
+]
  2. First observed

TDQS

A4.3/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=false, so safety is covered. The description adds useful behavior beyond that: each leg carries its own network, the returned card surfaces every amount, and execution is explicitly out of scope. It stops short of describing failure modes (e.g. unsupported asset or missing network), which the schema only partially implies.

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?

The core purpose and the amount-direction distinction are front-loaded, and the closing sentence prevents the most likely misuse. The intent-persona sentence ('For someone who wants to swap, convert or exchange crypto, asks how much...') is somewhat verbose but earns its place by covering paraphrases an agent must match.

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?

For a read-only, no-output-schema quote tool with fully documented parameters, the description covers what is queried, the two amount modes, per-leg networks, and the execution boundary. Only edge-case behavior on unresolvable networks/assets is left unstated, which is minor here.

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 the six parameters are already fully documented, including the amount-vs-receive_amount mutual exclusivity and network fallback behavior. The description restates the sent-amount/receive-amount duality and gives network examples, but adds no syntax or resolution detail beyond the schema, so this sits at the baseline.

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?

Opens with a specific verb and resource: a Cambio quote for swapping one crypto asset to another, for an exact amount sent or received, including comparison to other exchanges. It is clearly a read-only pricing tool, distinguishable from the sibling track_swap (which follows an existing swap) and gas_help (which covers network fees).

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?

Explicitly enumerates the user intents that should route here — wants to swap/convert/exchange, asks how much they would receive, or how much they must send. It also states the boundary that matters most: 'The swap itself is created on cambio.one or in Telegram from the card’s buttons, never here', so an agent knows not to look for execution here.

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

All Cambio toolsInspect
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