Skip to main content
Glama

iEscrow Marketplace (read-only)

Live offers to swap one crypto for another

get_swap_quote
Read-onlyIdempotent

Best live offers on the iEscrow marketplace to swap one crypto for another, for the given amount. Both legs are held in escrow, so there is no payment account and no bank involved. The platform fee is charged on EACH leg separately, so the reply states what the user would deliver fee included and what they would receive net. Give either give_amount or get_amount, not both. No account needed to look; taking an offer needs an iEscrow account. For crypto against government money use get_quote instead.

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": {
      "give_currency": "<give_currency>",
      "get_currency": "<get_currency>"
    },
    "name": "get_swap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
get_amountNoAmount the user wants to receive. Give this OR give_amount.
give_amountNoAmount the user wants to deliver. Give this OR get_amount.
get_currencyYesCrypto the user receives, e.g. BTC
give_currencyYesCrypto the user delivers, e.g. USDT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: both legs are escrowed with no payment account or bank, the platform fee is charged on EACH leg separately, and the reply reflects fee-included outflow and net inflow. That fee-on-both-legs detail materially changes how an agent interprets returned amounts.

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?

Five short sentences, front-loaded with what the tool returns and immediately followed by the escrow/fee rationale and the sibling routing rule. Nothing is padding; even the fee sentence does work by framing the amounts.

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?

Strong coverage for a 5-parameter read tool with no output schema: it explains the escrow model, fee treatment, amount semantics, auth requirements, and the alternative tool. The one gap is the `limit` parameter (1-20), which is undocumented in both schema and description, leaving an agent unsure what it caps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3; the description earns an extra point by explaining the economic meaning of give_amount and get_amount (deliver fee-inclusive vs receive net) and restating the one-or-the-other constraint. It misses the `limit` parameter entirely, which has no schema description either.

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?

Names a specific verb and resource ("Best live offers ... to swap one crypto for another") and scopes it to the iEscrow marketplace and a given amount. It explicitly distinguishes itself from the sibling get_quote by domain (crypto-to-crypto vs crypto-to-fiat), so an agent can route correctly without opening either 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?

Gives explicit when-to-use (crypto-for-crypto swap quotes) and when-not ("For crypto against government money use get_quote instead"), plus the mutually exclusive give_amount/get_amount rule. It also states the account prerequisite boundary: browsing needs none, taking an offer does.

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.