Skip to main content
Glama
AllRates-Today

Central Bank Rates MCP Server

by AllRates-Today
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List covered central banks & tax authorities

list_central_banks
Read-only

Discover which central banks are covered and obtain the bank codes required for rate lookups. Returns detailed listings for 60+ institutions including names, countries, and rate types.

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 60+ institutions — 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already mark this as read-only, and the description adds useful behavioral context: it returns a specific shape, covers 60+ institutions, includes tax authorities as well as central banks, and notes that it is cheap to call. This is more than annotations alone provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three focused sentences with the most important instruction front-loaded. Every sentence adds value: when to call, what is returned, and how the result connects to other tools.

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 no-parameter, read-only discovery endpoint, the description is complete enough even without an output schema. It names the key fields of the response, explains coverage, and gives concrete usage triggers.

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 takes zero parameters, so the baseline is 4. The description correctly focuses on what the response provides rather than parameter details, and the input schema already confirms no arguments are needed.

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 clearly states a specific verb and resource: listing covered central banks and tax authorities. It also distinguishes this discovery tool from rate/history/calendar siblings by emphasizing it is the lookup for bank codes.

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 instructs to call this FIRST when a bank code is needed, and shows example user queries that should trigger it. It also explains that the returned `code` is the parameter used by every other tool, making the relationship to alternatives explicit.

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

Deploy Server

Other Tools