Skip to main content
Glama
AllRatesToday MCP Server

AllRatesToday MCP Server

List covered central banks & tax authorities

list_central_banks
Read-only

Find the bank code and coverage status for 130+ central banks and tax authorities, including latest publication dates and schedule delays, before requesting official rates.

Instructions

Call this FIRST when you need a bank code, or for 'which central banks do you cover?' / 'do you have rates from X?'. Returns every covered source — 130+ central banks and tax authorities (HMRC, US Treasury, Swiss BAZG, India CBIC, Peru SUNAT) — with code (what get_official_rates takes as bank), name, latest publication date and whether it is behind schedule. No API key needed.

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

Output Schema

NameRequiredDescriptionDefault
sourcesYes
checked_atYes
stale_countYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.9

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral details: it returns code, name, latest publication date, and schedule status for 130+ sources, and that no API key is needed. It does not mention pagination or rate limits, but with zero parameters these are unlikely to be critical.

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?

The description is three sentences, front-loaded with the primary usage instruction, and includes only illustrative examples and a key behavioral note (no API key needed). There is no redundant or vague wording.

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 zero-parameter list tool with an output schema and read-only annotations, the definition covers what the tool returns, when to use it, and the no-auth requirement. Nothing critical is missing for correct invocation.

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?

There are zero input parameters, so the baseline is 4. The description adds meaning by clarifying that the returned `code` field is what get_official_rates expects as `bank`, but there are no input parameters to document.

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 states a specific verb (list) and resource (central banks & tax authorities), and it explicitly distinguishes the tool from get_official_rates by explaining that the returned `code` is what get_official_rates takes as `bank`. An agent can identify the tool's role without reading the schema.

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 instructs to 'Call this FIRST when you need a bank code' and names the exact queries it answers ('which central banks do you cover?', 'do you have rates from X?'). It also points to get_official_rates as the follow-up for rates, giving clear when-to-use guidance and an implicit alternative.

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