Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Convert USD to another currency

convert_from_usd
Read-only

Calculate how much of a target currency a USD amount buys at current Futuur exchange rates, returning the converted amount and rate without exchanging funds.

Instructions

Calculates how much of another currency a USD amount buys at Futuur's latest exchange rates. It only calculates; nothing is exchanged and no balance changes. Use it to express a USD amount in USDC, USDT, EUR, BTC, ETH and other quoted currencies (see get_exchange_rates for the list). Play money (OOM) has no USD rate. Returns the converted amount, the rate used (units of the target currency per 1 USD) and when the rates were updated.

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": {
      "value": "<value>",
      "to_currency": "<to_currency>"
    },
    "name": "convert_from_usd"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesAmount in USD to convert, greater than 0.
to_currencyYesTarget currency code, e.g. "BTC", "USDC" or "EUR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses that the tool only calculates, that nothing is exchanged and no balance changes, and that rates are 'latest' rather than user-supplied — the key behavioral facts for an agent deciding whether a side-effect-free conversion is safe to call.

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?

Four tightly packed sentences, front-loaded with the core action, then safety, then currency scope, then return shape. The 'only calculates; nothing is exchanged and no balance changes' clause is slightly redundant but earns its place as the primary safety cue.

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?

With no output schema, the description compensates by naming the three returned fields (converted amount, rate used, rates-updated timestamp) and defines the rate's unit basis, so an agent knows exactly what it will get back from this two-parameter conversion tool.

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 100% so the two parameters are already documented; the description adds meaning the schema lacks by defining the rate as 'units of the target currency per 1 USD', listing supported currency examples, and excluding OOM from valid to_currency values (the schema has no enum).

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 — calculating how much of another currency a USD amount buys at Futuur's latest rates — and names both the input currency (USD) and the target set (USDC, USDT, EUR, BTC, ETH), which disambiguates it from the reverse-direction sibling convert_to_usd.

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 usage context (express a USD amount in a quoted currency), an explicit exclusion (play money OOM has no USD rate), and routes to get_exchange_rates for the authoritative currency list rather than guessing the domain.

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