Skip to main content
Glama

Convert crypto and fiat amounts at the current spot rate

crypto_convert
Read-only

Convert an amount between a crypto and a fiat currency, or between two crypto assets, at the current spot price: the rate, the converted amount, the pair path used (direct, or through USD) and the time of the rate. Spot prices from Coinbase, Kraken as the fallback. A spot rate, not an executable quote: no fees or slippage. Fiat to fiat is refused; use the FX tool for that. Information only, not financial advice. Related tools on this server, for a different need: crypto_price when you need USD spot prices for up to 20 symbols from Coinbase; crypto_candles when you need OHLCV candles for a Coinbase trading pair at 1m, 5m, 15m. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": "<from>",
      "to": "<to>"
    },
    "name": "crypto_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesSymbol to convert to, e.g. EUR, USD or ETH
fromYesSymbol to convert from: BTC, ETH, SOL, USDC or a fiat code such as EUR
amountNoPositive amount in the from currency, up to 12 decimals (default 1)

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
pathNo
rateNo
amountNo
sourceNo
checkedAtNo
convertedNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial context beyond that: upstream sources (Coinbase with Kraken fallback), routing behavior (direct or through USD), non-executable quote semantics, an explicit refusal case, and metered billing ('$0.002 per successful call, paid with x402... failed calls are not charged'). This is exactly the cost and failure-profile information an agent needs before invoking a paid endpoint.

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 operation, its rate basis and its output fields are front-loaded in the first two sentences, and the alternative-tool routing sits at the end where it is easy to skim. It runs long for a single-sentence-able tool, with pricing boilerplate and the 'not financial advice' disclaimer consuming space, but almost every clause carries decision-relevant information.

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?

For a 3-parameter read-only conversion tool with an output schema, the definition covers everything an agent needs: inputs, output fields, rate provenance, refusal cases, and cost model. Return values are described even though an output schema exists, which is redundant but not harmful, and no operational question is left open.

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 schema already documents from, to and amount including the default of 1 and the 12-decimal limit. The description adds one genuine constraint beyond the schema — that fiat-to-fiat pairs are rejected and belong to the FX tool — but otherwise restates the supported symbol types the schema already lists. Baseline 3 given schema coverage.

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?

States a specific verb and resource ('Convert an amount between a crypto and a fiat currency, or between two crypto assets') plus the exact rate basis ('current spot price'). It also enumerates the returned fields line by line, making it unmistakable versus crypto_price (USD spot prices for symbols) and crypto_candles (OHLCV).

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?

Explicit exclusions and alternatives are named: 'Fiat to fiat is refused; use the FX tool for that', 'crypto_price when you need USD spot prices for up to 20 symbols', and 'crypto_candles when you need OHLCV candles'. It also scopes itself as 'a spot rate, not an executable quote: no fees or slippage', so the agent knows when this is the wrong tool for an execution use case.

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