Skip to main content
Glama
mcp-server-cnb-cache

mcp-server-cnb-cache

by Spoje-NET

Get Exchange Rate

get_rate
Read-onlyIdempotent

Fetch the Czech National Bank exchange rate for a currency on a chosen date or recent day, returning how many CZK equal the requested amount.

Instructions

Get the CNB exchange rate (CZK per amount units) of one currency for a given day.

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": {
      "currency": "<currency>"
    },
    "name": "get_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageNoDays back from today; ignored if date is given
dateNoDay as YYYY-MM-DD (default: today)
currencyYesISO 4217 code, e.g. EUR, USD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive, so the safety profile is covered. The description adds genuinely useful context: the data source is CNB and the rate direction is CZK per unit of the requested currency. It omits behavior an agent needs, notably what is returned for weekends/holidays when CNB does not publish, or whether a fallback date is used.

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?

A single well-formed sentence with the action and the qualifiers front-loaded and no wasted clauses. The only defect is the undefined `amount` reference, which is a correctness issue rather than verbosity.

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?

An output schema exists, so return values need not be explained, and the input schema fully documents the three parameters. For a simple single-lookup tool the description covers purpose, source and rate direction; only non-publishing-day behavior is unstated, which is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents currency, date and age (including 'age ignored if date is given'). The description instead references an `amount` unit that does not exist in the schema, which can mislead an agent into looking for a nonexistent parameter, and it adds no clarification of the age/date precedence beyond what the schema says.

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?

The description states a concrete verb and resource ('Get the CNB exchange rate') and pins scope to 'one currency for a given day', which implicitly separates it from a history tool. It does not name get_rate_history or convert_amount, so no explicit sibling differentiation is provided.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'For a given day' implies a single-point lookup rather than a series, which is some when-to-use signal. However, there is no exclusion guidance (e.g. use get_rate_history for ranges, convert_amount for arithmetic) and no stated prerequisites.

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