Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Convert amount to USD

convert_to_usd
Read-only

Converts an amount in a supported currency to its USD equivalent using Futuur exchange rates for balances or stakes; it only calculates and does not exchange funds.

Instructions

Calculates what an amount in another currency is worth in USD at Futuur's latest exchange rates. It only calculates; nothing is exchanged and no balance changes. Use it to show a USD equivalent for a balance or a stake in USDC, USDT, EUR, BTC, ETH and other quoted currencies (see get_exchange_rates for the list). Play money (OOM) has no USD value. Returns the converted amount, the USD rate used 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>",
      "from_currency": "<from_currency>"
    },
    "name": "convert_to_usd"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYesAmount of the source currency to convert, greater than 0.
from_currencyYesSource currency code, e.g. "BTC", "USDC" or "EUR".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds meaningful behavior beyond them: nothing is exchanged, no balance changes, OOM is excluded, and the return payload includes the converted amount, rate used, and rate-update time. This is strong disclosure for a read-only utility, with only minor room for more (e.g., rounding behavior).

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 tight sentences, front-loaded with the core purpose and followed by usage, constraints, and return values. No filler; every sentence carries information, though a slightly shorter version could preserve the same content.

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 return fields (converted amount, USD rate, rate timestamp). It also covers the key constraint (OOM unsupported) and the non-mutating nature, making it complete for a simple two-parameter calculation tool.

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 100%, so both parameters are fully documented in the input schema. The description adds only domain context for from_currency (examples of quoted currencies and a pointer to get_exchange_rates) and no new meaning for value, so baseline 3 applies.

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?

The description states a specific verb and resource ('Calculates what an amount in another currency is worth in USD') with clear scope: a pure calculation at Futuur's latest rates. It distinguishes itself from a generic conversion tool by specifying direction (to USD) and the data source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete use cases ('show a USD equivalent for a balance or a stake') and a when-not condition ('Play money (OOM) has no USD value'), plus a pointer to get_exchange_rates for supported currencies. It stops short of explicitly contrasting with the reverse-direction sibling convert_from_usd, leaving a small gap.

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