Skip to main content
Glama
Futuur MCP

Futuur MCP

Official
by futuur

Get exchange rates

get_exchange_rates
Read-only

Retrieve Futuur currency exchange rates for all supported base currencies or filter by USD, EUR, BTC, USDC, or USDT to compare quoted currency values and last update times.

Instructions

Returns Futuur's latest currency exchange rates. Each entry is a base currency (USD, EUR, BTC, USDC, USDT) with rates: how many units of every quoted currency (BCH, BNB, BRL, BTC, ETH, EUR, LTC, MXN, SOL, TRX, USD, XMR, BUSD, DOGE, USDC, USDT) one unit of the base is worth, and the time of the last update. Play money (OOM) has no rate. Pass base_currency to get one base only; use convert_to_usd or convert_from_usd to convert an amount.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_exchange_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
base_currencyNoReturn only this base currency's rates: USD, EUR, BTC, USDC or USDT (case-insensitive). Omit for all bases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuine value by enumerating the supported bases and quoted currencies, explaining the `rates` semantics (units per one unit of base), and noting the edge case that play money (OOM) has no rate. It does not mention refresh frequency or caching expectations, so it falls short of exhaustive.

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 the purpose, then structure, then edge case, then routing — a sensible order with no filler sentences. The long inline currency enumeration is verbose, though it does convey real domain 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?

There is no output schema, so the description carries the burden of explaining return values — and it does so precisely, covering entry keys, the nested rates map, and the timestamp. For a single optional parameter read tool, nothing an agent needs is missing.

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% and already documents the allowed base values, case-insensitivity, and the omit-for-all behavior, so the description largely restates the schema. Its one contribution is clarifying that the supported base set is bounded and that OOM is not queryable, which is marginal added meaning.

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?

Opens with a specific verb and resource ("Returns Futuur's latest currency exchange rates") and immediately details the shape of each entry: base currency, `rates` map, and timestamp. This is clearly distinguishable from the conversion siblings and from account/balance tools.

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?

Explicitly states both modes — pass `base_currency` for a single base, omit for all — and names the alternatives (`convert_to_usd`, `convert_from_usd`) for amount conversion. An agent knows exactly when this tool is the right pick versus the converters.

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