Skip to main content
Glama

BRAINIAC Exchange Rates

Get historical exchange rates

fx_rates_historical

Retrieve exchange rates for a specific date from the Frankfurter API (ECB data). Returns rates for the closest working day. Price $0.02 USDC. POST /api/v1/fx/rates/historical. Unpaid calls return 402 and do not run.

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": {
      "date": "<date>"
    },
    "name": "fx_rates_historical"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNo
dateYes
symbolsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a lot: it discloses the POST endpoint, the $0.02 USDC cost, that unpaid calls return 402 and do not execute, and the important fallback behavior of returning the closest working day. It leaves open the response shape and what happens with malformed or future dates, but the payment and fallback traits are exactly the kind of non-schema behavior an agent needs.

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 short, front-loaded sentences: purpose first, then fallback semantics, then price and transport, then failure mode. No filler. The endpoint path and price are operational facts, though the path adds limited value to an agent that never constructs URLs directly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a paid, unannotated, single-date rate tool with no output schema, the description covers the payment gate and date fallback well. It is still incomplete on currency selection semantics and default base, and gives no hint about the returned rate structure, so an agent cannot fully predict the call's shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, yet it only clarifies the meaning of `date` (single date, nearest working day). It says nothing about `base` (source currency, likely defaulted) or `symbols` (target currencies, string vs array, whether omitted means all), leaving two of three parameters undocumented anywhere.

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?

States a specific verb and resource (retrieve exchange rates) scoped to a single date and names the data source (Frankfurter API / ECB), which implicitly separates it from the latest and timeseries siblings. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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?

The phrase 'for a specific date' implies a single-day lookup rather than a range or the latest snapshot, giving implied guidance. There is no explicit statement of when to prefer this over fx_rates_latest or fx_rates_timeseries, and no note on error or out-of-range dates.

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