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

mcp-server-cnb-cache

by Spoje-NET

Get Rate History

get_rate_history
Read-onlyIdempotent

Retrieve daily Czech National Bank exchange rates for one currency over a date range of up to 31 days, skipping dates without a published rate.

Instructions

Get daily CNB rates of one currency over a date range (max 31 days). Days without a published rate are skipped.

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>",
      "from_date": "<from_date>"
    },
    "name": "get_rate_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_dateNoLast day, YYYY-MM-DD (default: today)
currencyYesISO 4217 code, e.g. EUR
from_dateYesFirst day, YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new behavior: a hard 31-day range limit and the fact that days without a published rate are silently skipped, which affects how an agent interprets a returned series. It does not say what happens if the range exceeds 31 days (error vs truncation).

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?

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the constraints. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the description covers the key operational facts: range cap and skipped non-publication days. Minor gaps remain around behavior when the cap is exceeded and whether from_date/to_date ordering is enforced.

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

Parameters3/5

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

Schema description coverage is 100%, so currency code format, date formatting and the to_date default of today are all documented in the schema. The description adds no semantics beyond that, which is the expected baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ("Get daily CNB rates of one currency") plus scope ("over a date range"), which clearly separates it from a single-date lookup like get_rate. It stops short of naming the sibling to route away from, so it is clear but not fully differentiated.

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?

Usage is implied by the range-based framing, and the 31-day cap hints at when this tool is appropriate. There is no explicit when-to-use/when-not-to-use guidance and no mention of the alternatives (get_rate, convert_amount) for single-date or conversion needs.

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