Skip to main content
Glama
Central Bank Rates MCP Server

Central Bank Rates MCP Server

List covered central banks & tax authorities

list_central_banks
Read-only

Retrieve supported central banks and tax authorities with codes, names, countries, currencies, rate types, and latest dates so you can pick the correct bank parameter before requesting rates.

Instructions

Call this FIRST when you need a bank code, or when the user asks 'which central banks do you cover?' or 'do you have rates from X?'. Returns { banks: [{ code, name, country, home_ccy, rate_types, latest date, ... }], disclaimer } for 130+ central banks and tax authorities (plus a composite) — central banks (ECB, Fed, BOJ, ...) plus tax authorities (HMRC, US Treasury, ...). The code field is what every other tool takes as its bank parameter. Cheap to call.

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": "list_central_banks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.6/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 the safety profile is covered. The description adds value beyond that: it sketches the return object ({ banks: [...], disclaimer }), reports coverage scale (130+), and notes the call is cheap, which helps an agent decide to call it freely. It stops short of describing pagination or ordering, but that is minor for a small static catalog.

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 action rule and the trigger phrases before the return shape and coverage detail, which is the right order. There is mild redundancy in enumerating examples twice ('ECB, Fed, BOJ' then 'HMRC, US Treasury'), but nothing that obscures the point.

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 parameters and no output schema, the description carries the burden and does so: it defines the return envelope, the salient fields, the institution count, and the cross-tool contract for `code`. An agent has everything needed to call it and use 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?

The tool has zero input parameters, so there is nothing for the description to disambiguate on the input side. It instead documents the output field semantics — `code` being the value other tools accept as `bank` — which is genuinely useful cross-tool context.

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?

States a specific verb and resource (list covered central banks & tax authorities) and immediately frames the tool as a lookup/discovery step that yields bank codes. It distinguishes itself from siblings by explaining that the returned `code` is the `bank` input every other tool takes, which no sibling does.

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 says 'Call this FIRST when you need a bank code' and gives concrete trigger phrasings ('which central banks do you cover?', 'do you have rates from X?'). This is a clear when-to-use rule rather than implied usage.

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