Skip to main content
Glama

Historical exchange rates

blackwood_fx_history
Read-onlyIdempotent

Use when you need historical exchange rates, a historical FX rate series, forex history or a currency trend. Do not use for rates older than 90 days, live quotes or crypto (one ECB rate per business day). Returns JSON with historical exchange rates: 90 days of daily ECB euro reference rates (free at ecb.europa.eu) for up to 10 currencies, rebased to any base as cross rates, with min, max and percent change for 0.005 USDC per call. Typical response time 1500 ms (p95). Category: Data.

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": {
      "symbols": "<symbols>"
    },
    "name": "blackwood_fx_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
baseNoBase currency, ISO 4217 (EUR when omitted), e.g. USD
daysNoCalendar days back from endDate, 1 to 90 (90 when omitted; ignored with startDate), e.g. 30
endDateNoLast day, YYYY-MM-DD (latest ECB day when omitted), e.g. 2026-09-30
symbolsYesCurrencies to return, ISO 4217, up to 10, e.g. ["USD", "BRL"]
startDateNoFirst day, YYYY-MM-DD, within the last 90 days, e.g. 2026-09-01
response_formatNoconcise (the default when omitted) keeps the JSON short: long fields such as base64 images or audio come back as separate image/audio content blocks and other long strings are cut with a marker; detailed returns the full JSON

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description goes well beyond them: ECB as the source, one rate per business day, 90-day ceiling, up to 10 currencies, cross-rate rebasing, cost of 0.005 USDC per call, and p95 latency of 1500 ms. Cost and latency disclosures in particular are exactly the kind of operational context annotations cannot carry.

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 use condition, then exclusions, then behavior and limits — a good ordering with no filler sentences. The opening list of near-synonyms ('historical exchange rates, a historical FX rate series, forex history or a currency trend') is somewhat redundant keyword padding that a 5 would have trimmed.

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 6-parameter, read-only data tool with a full schema and an output schema, the description supplies everything else an agent needs: data source, coverage window, currency cap, pricing, latency, and explicit exclusions. Return-value shape is correctly left to the output schema.

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 baseline is 3; the description adds real meaning on top by explaining that results are 'rebased to any base as cross rates', which clarifies how the base parameter actually behaves, plus the derived min/max/percent-change outputs. It does not clarify startDate/days interaction or response_format beyond the schema.

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+resource ('historical exchange rates', 'historical FX rate series') and clearly delimits scope to historical ECB data. It does not name or differentiate from the near-identical sibling blackwood_fx_rates, which is the one sibling an agent is most likely to confuse it with, so it falls short of a 5.

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?

Gives explicit when-to-use ('need historical exchange rates... currency trend') and when-not ('rates older than 90 days, live quotes or crypto'), which is strong routing guidance. It stops short of naming the alternative tool (blackwood_fx_rates) for the live-quote case, so the agent must infer the substitute.

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