Skip to main content
Glama
Central Bank Rates MCP Server

Central Bank Rates MCP Server

Get a bank's official published rates

get_official_rates
Read-only

Fetch official central bank and tax authority exchange rates for compliance, invoicing, and accounting, with optional date-specific lookup.

Instructions

Use this for OFFICIAL rates a specific institution published — 'what is the ECB rate for USD?', 'Bank of Japan official rate on 2026-03-14', 'HMRC rate for invoicing'. These are the fixed rates in force for compliance, tax, customs, and accounting — NOT live market rates. Omit date for the newest published table; give date (paid plans) for the table in force on that day (weekends/holidays roll back to the last published date — the response's rate_date says which). Omit source/target for the bank's full table { rates: [{ base, quote, type, value }] }; give both for one pair — with an API key, pairs not directly published are cross-computed via the bank's own home currency and flagged derived; keyless serves only published pairs and their inverses. For live mid-market rates use the @allratestoday/mcp-server package instead.

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": {
      "bank": "<bank>"
    },
    "name": "get_official_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
bankYesBank/authority code as returned by list_central_banks (lowercase, e.g. 'ecb', 'fed', 'boj', 'hmrc', 'cbsl'). Call list_central_banks first if unsure — codes are short abbreviations of the institution, not country codes.
dateNoOptional YYYY-MM-DD. Omit for the latest published table (all plans). A specific date requires a paid plan.
sourceNoOptional. With target, narrows to one pair.
targetNoOptional. With source, narrows to one pair.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

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 plan gating (specific dates require a paid plan), non-obvious date semantics (weekends/holidays roll back to the last published date, with rate_date in the response saying which), keyless vs. keyed behavior, and that cross-computed pairs are cross-computed via the bank's home currency and flagged `derived`.

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?

Information is front-loaded: purpose, then exclusions, then parameter behavior, then the alternative tool. It is dense and clause-heavy in one paragraph, but nearly every clause adds operative detail, so little is wasted.

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, yet the description supplies the return shape and the rate_date field, plus how omitted parameters change that shape. For a four-parameter read tool with one required argument, an agent has everything needed to call it correctly and interpret the result.

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 already 100%, so the baseline is 3; the description goes further by explaining what the parameter combinations produce (full table shape { rates: [{ base, quote, type, value }] } vs. a single pair) and by clarifying the paid-plan and derived-pair consequences. It stops short of restating the bank-code format, which the schema already covers well.

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 names a specific verb and resource ('OFFICIAL rates a specific institution published') and anchors it with three concrete user phrasings (ECB, Bank of Japan, HMRC invoicing). It explicitly separates itself from live market rates, which is the key disambiguation against the sibling rate 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?

It states exactly when to use this tool (compliance, tax, customs, accounting, fixed published rates) and when not to ('NOT live market rates'), pointing to a named alternative for live mid-market rates. It also gives conditional guidance for each parameter permutation — omit date vs. supply date, omit source/target vs. supply both.

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