Skip to main content
Glama

Cnb Cz

by io.github.pipeworx-io

Cnb Pribor

cnb_pribor
Read-onlyIdempotent

PRIBOR — the Prague Interbank Offered Rate (CZK money-market reference rates) for a given day. Returns one entry per tenor (period: ONE_DAY, ONE_WEEK, ONE_MONTH, THREE_MONTH, SIX_MONTH, ONE_YEAR, etc.) with the pribor rate in percent. Omit date for the latest. Verified live.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDay in YYYY-MM-DD, e.g. "2026-05-27". Omit for the latest. Weekends/holidays return the last valid working-day fixing.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate safe, idempotent read operation. The description adds behavioral details: returns data per tenor, rates in percent, 'verified live', and handling of weekends/holidays. No contradictions.

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 concise sentences with no fluff. Key information front-loaded: what it returns, tenors, omission option, and verification status.

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?

For a simple tool with one optional parameter and no output schema, the description covers input behavior, output structure (per tenor), and verification. Could potentially include which fields are returned, but it's sufficient.

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 covers the 'date' parameter well. The description adds meaning by reiterating omission for latest and explaining weekend behavior, going beyond the schema's description.

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 it returns PRIBOR rates for a given day, with specific tenors. It is distinct from sibling tools like cnb_czeonia or cnb_exchange_rates, which cover different 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 implies when to use via 'Omit date for latest' and weekends fallback, but does not explicitly state when not to use or compare with alternatives like cnb_czeonia.

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