Skip to main content
Glama

get_cnb_exchange_rates

Fetch official Czech National Bank daily or historical DUZP FX rates and convert amounts to or from CZK using an optional date, amount, and currency code.

Instructions

Fetch official Czech National Bank (CNB) daily or historical DUZP FX rates and convert amounts into/from CZK.

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

Input Schema

NameRequiredDescriptionDefault
dateNoOptional date in DD.MM.YYYY format
amountNoOptional amount to convert between currency and CZK
currencyNoOptional 3-letter currency code, e.g. EUR or USD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It identifies the data source as the official CNB and the rate types as daily/historical DUZP, and 'Fetch' implies read-only access, but it does not mention authentication, rate limits, caching/freshness, or error behavior.

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 front-loaded sentence names the source, rate type, and conversion scope with no filler. It is appropriately sized for a simple fetch/convert tool.

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

Completeness3/5

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

The tool is simple and the input schema fully documents all three optional parameters, but the description does not explain default behavior when date, amount, or currency are omitted, nor what the response contains (there is no output schema). These gaps are material for an agent deciding how to call it.

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 the baseline is 3. The description adds that amounts are converted into/from CZK and that rates are DUZP, but it does not clarify defaults or how the optional date, amount, and currency parameters interact.

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 names a specific verb (fetch), resource (official Czech National Bank daily or historical DUZP FX rates), and conversion operation, making the purpose clear. It does not explicitly distinguish itself from any sibling, though the resource is unique among the listed tools.

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

Usage Guidelines2/5

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

It states capabilities but gives no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is for CNB FX/DUZP rates or CZK conversion from the purpose statement alone.

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