Skip to main content
Glama

get_quote

Read-only

Get a quote for a swap (onramp quotes are signed by the API). Pass the returned object unchanged to create_order.

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": {
      "src_chain": "<src_chain>",
      "dst_chain": "<dst_chain>",
      "src_token": "<src_token>",
      "dst_token": "<dst_token>",
      "amount": "<amount>",
      "recipient": "<recipient>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to swap as an integer string in the source token's smallest unit
senderNoAddress sending the funds, encoded for the source chain. On onramps it lets create-order return a funded PSBT, which may spend the address's ordinals, inscriptions or runes as plain sats: omit it for an address holding any.
slippageNoSlippage tolerance in basis points (max 1000). Omit to let the gateway pick one per route.
dst_chainYesDestination chain
dst_tokenYesDestination token address; "0x0000000000000000000000000000000000000000" for BTC/native
recipientYesAddress receiving the funds, encoded for the destination chain
src_chainYesSource chain, e.g. "bitcoin", "ethereum", "base", "bob", "tron"
src_tokenYesSource token address; "0x0000000000000000000000000000000000000000" for BTC/native
affiliatesNoAffiliate fees as comma-separated `<address>:<bps>` pairs, e.g. "0xabc...:50". Addresses are EVM, except on a token swap to Tron, where a Tron address is also accepted.
refund_addressNoRefund address on the source chain. Optional here, required by create-order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description does add non-obvious context: onramp quotes are signed server-side, and the returned object must be passed through unmodified. However, for a quote tool the most critical behavioral facts are missing - whether quotes expire, how long they are valid, and whether the returned object is bound to the requesting parameters.

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 short sentences with zero filler; the core action is front-loaded and the parenthetical caveat is scoped tightly to onramps. Every clause earns its place.

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

Completeness3/5

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

With ten parameters and no output schema, the description should explain more about what the quote object contains and how long it remains usable before the agent blindly forwards it to create_order. The pass-through instruction covers the main workflow gap, but quote validity and return shape remain unaddressed.

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 every one of the ten parameters is already documented in detail, including the sender ordinals warning and slippage bounds. The description adds nothing beyond that, which is the expected baseline given the schema carries the full parameter burden.

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 ('Get a quote for a swap') and names the downstream sibling create_order, so the agent knows this is the read-only quoting step. It does not distinguish itself from the closer sibling quote_and_create, which an agent could easily confuse it with.

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 implied through the chaining instruction ('Pass the returned object unchanged to create_order'), which tells the agent this is the preamble to order creation. There is no explicit when-not guidance and no mention of quote_and_create or get_routes as alternatives, so the agent must infer the choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources