Skip to main content
Glama

iEscrow Marketplace (read-only)

Live offers to buy or sell crypto with fiat

get_quote
Read-onlyIdempotent

Best live offers on the iEscrow P2P marketplace for buying or selling crypto with fiat money, for the given crypto amount: price with the maker's margin, what the user would pay or receive all-in (platform fee included), whether it is instant and the accepted payment methods. No account needed to look. In every trade the crypto is locked in escrow BEFORE the fiat is paid, and released when the seller confirms the payment arrived. Taking an offer needs an iEscrow account: on the web at the marketplace, or with the agent connected to the full server.

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": {
      "side": "<side>",
      "crypto": "<crypto>",
      "fiat": "<fiat>",
      "amount": "<amount>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
fiatYesFiat ISO code, e.g. ARS, USD, BRL, EUR
sideYesbuy = the user pays fiat and receives crypto; sell = the user delivers crypto and receives fiat
limitNo
amountYesAmount in CRYPTO units
cryptoYesCrypto symbol, e.g. USDT, BTC, ETH
payment_methodNoOptional payment method name to filter (e.g. 'Mercado Pago', 'PIX')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive open-world read. The description adds genuinely new context: no account is required to view offers, taking an offer requires an iEscrow account on web or a full-server-connected agent, and every trade is escrow-backed with crypto locked before fiat is paid. That trust/permission framing goes beyond the annotations; rate limits and result paging are the only notable omissions.

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?

Front-loaded with what the tool returns, then the escrow and account prerequisites in two compact sentences. The escrow mechanics are slightly tangential to calling the tool, but they justify the safety of the data and earn their place.

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?

With no output schema, the description carries the return-value burden and does so well: price with maker margin, all-in cost including platform fee, instant eligibility, accepted payment methods. The gaps are the limit parameter and the payment_method filter, which are left entirely to the 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 83%, so the schema already documents side, fiat, crypto, amount and payment_method. The description only reinforces that the amount is in crypto units and that payment methods are surfaced in results; it says nothing about the undocumented 'limit' parameter (1-20) or that payment_method acts as a filter.

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?

A specific verb-plus-resource statement: live offers on the iEscrow P2P marketplace for buying or selling crypto with fiat, scoped to a given crypto amount. It also names what the response contains (price with margin, all-in amount, instant flag, payment methods). It does not distinguish itself from the sibling get_swap_quote, so an agent must infer which quoting tool to pick.

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 rather than stated: it tells the agent an account is not needed to look but is needed to actually take an offer, which frames this as a browse/preview step. There is no explicit guidance on when to prefer this over get_swap_quote, nor any when-not condition.

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.