Skip to main content
Glama

Cnb Cz

by io.github.pipeworx-io

Cnb Exchange Rates

cnb_exchange_rates
Read-onlyIdempotent

ČNB official daily exchange rates against the Czech koruna (CZK) for a given day. Returns one entry per listed currency (~30 currencies, e.g. USD, EUR, GBP, JPY) with country, currency, currencyCode, amount and rate. The rate is CZK per amount units of that currency. Omit date for the latest published rates. Verified live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDay in YYYY-MM-DD, e.g. "2026-05-27". Omit for the latest published rates. Weekends/holidays return the last valid working-day rates.
langNoLabel language: "EN" (default) or "CZ".

TDQS

A3.9/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool returns ~30 currencies per entry with specific fields and explains the rate meaning. It also notes that weekends/holidays return last valid rates.

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?

The description is three sentences, front-loaded with the main purpose, and includes necessary details without redundancy. It is appropriately sized.

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 no output schema, the description adequately explains return structure (one entry per currency with fields) and date behavior. It covers the key aspects, though missing details about error handling or pagination (likely unnecessary for simple data).

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 coverage is 100%, so the schema already documents both parameters. The description restates the optional nature of date and the default lang, adding minimal extra context like 'Verified live.'

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 clearly states the tool provides ČNB official daily exchange rates against CZK, specifying the source, target currency, and frequency. It distinguishes from siblings like cnb_exchange_rates_currency_month and cnb_monthly_averages by focusing on daily rates.

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?

The description explains how to use the date parameter (omit for latest, weekends/holidays return last valid), but does not explicitly guide when to choose this tool over sibling CNB tools for different periods or currencies.

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

All Cnb Cz toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Tools have distinct purposes overall, but some pairs (e.g., ask_pipeworx vs ask_pipeworx_grounded, entity_profile vs recent_changes) could cause agent confusion without careful reading. Descriptions mitigate overlap, so only minor ambiguity.

Naming Consistency4/5

Most tools use snake_case with verb_noun or noun_verb patterns, but several single-word verbs (forget, recall, remember, subscribe) and a few inconsistent forms (czeonia, pribor) break uniformity. Still, the pattern is largely predictable.

Tool Count4/5

31 tools is high but justified for a multi-domain data gateway covering finance, economics, FDA, betting, and subscriptions. Each tool has a clear role, though the count pushes the upper bound for easy scanning.

Completeness5/5

The tool set comprehensively covers its stated domains: entity resolution, financial data, exchange rates, interest rates, SEC filings, FDA, Polymarket analysis, subscriptions, and utility memory. No obvious gaps given its purpose as a data retrieval and analysis server.

Resources