Skip to main content
Glama

get_cnb_exchange_rates

Read-onlyIdempotent

Read Czech National Bank reference rates for the latest available fixing or a historical date. Omit currency to list rates. Supply currency and amount to return both its CZK equivalent and the foreign-currency equivalent of the same numeric amount in CZK. Check publishedDate for the actual fixing used.

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
dateNoFixing date in DD.MM.YYYY format, e.g. 16.11.2026. Omit for the latest available table.
amountNoNon-negative amount to convert. Requires currency. For example, currency EUR and amount 100 converts both 100 EUR and 100 CZK.
currencyNoThree-letter currency in the CNB table, e.g. EUR. Omit to list all quoted currencies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / amount / description
      Previous value: -"Optional amount to convert between currency and CZK"New value: +"Non-negative amount to convert. Requires currency. For example, currency EUR and amount 100 converts both 100 EUR and 100 CZK."
    • addedInput schema / properties / amount / minimum
      Added value: +0
    • changedInput schema / properties / currency / description
      Previous value: -"Optional 3-letter currency code, e.g. EUR or USD"New value: +"Three-letter currency in the CNB table, e.g. EUR. Omit to list all quoted currencies."
    • changedInput schema / properties / date / description
      Previous value: -"Optional date in DD.MM.YYYY format"New value: +"Fixing date in DD.MM.YYYY format, e.g. 16.11.2026. Omit for the latest available table."
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior – the bidirectional conversion result and the fact that the returned fixing may differ from the requested date, so check publishedDate. It stops short of describing rate-table staleness, missing-currency errors, or the shape of the returned list.

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

Conciseness4/5

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

Three short sentences with the core capability front-loaded, followed by the two usage modes and the correctness caveat. The second sentence is somewhat dense and slightly overlaps the amount parameter's schema example, but nothing is padding.

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?

All three optional parameters are accounted for, and with no output schema the description usefully names publishedDate as the field to inspect for the actual fixing. Minor gaps remain around error behavior for unknown currencies and how far back historical dates are supported.

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?

Schema coverage is 100%, so baseline is 3, but the description adds the semantic link that amount is only meaningful with currency and that both conversion directions are returned. That reinforces rather than duplicates the amount example in the schema, though it does not restate the date format or the three-letter currency constraint.

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?

States a specific verb and resource ("Read Czech National Bank reference rates") plus the two supported modes: latest fixing or a historical date. The sibling tools (website audit, company KYB, VAT/IBAN verification) do not overlap, so no sibling differentiation is needed, and an agent can route correctly from this sentence alone.

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

Usage Guidelines4/5

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

Gives actionable branching rules: omit currency to list the whole table, supply currency plus amount to get conversions. It does not spell out what happens when a requested date is a non-fixing day, though the closing hint to check publishedDate implies the fallback.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources