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

mcp-server-cnb-cache

by Spoje-NET

Convert Amount

convert_amount
Read-onlyIdempotent

Convert an amount between CZK and a foreign currency, or between two foreign currencies via CZK, using Czech National Bank exchange rates for a chosen day or today.

Instructions

Convert an amount between CZK and a foreign currency (or two foreign currencies via CZK) using CNB rates of a given day.

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": {
      "amount": "<amount>",
      "from_currency": "<from_currency>",
      "to_currency": "<to_currency>"
    },
    "name": "convert_amount"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay as YYYY-MM-DD (default: today)
amountYesAmount in the source currency
to_currencyYesTarget code, e.g. CZK, EUR
from_currencyYesSource code, e.g. CZK, EUR

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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 real value by disclosing the CNB rate source and the CZK triangulation path for two-foreign-currency conversions, but says nothing about rounding/precision or failure modes for currencies not in the CNB list.

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 with no filler; the parenthetical about CZK triangulation carries genuinely useful information rather than restating the name.

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 and full parameter coverage, the description covers what an agent needs to select and invoke the tool. The one gap is precision/rounding of the converted result, which matters for an amount-conversion tool.

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 all four parameters (including the date default of today) are already documented. The phrase 'rates of a given day' reinforces the date parameter's meaning but adds no syntax or constraint details beyond the schema.

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?

Names a specific verb (convert) and resource (amount) and discloses the rate source (CNB rates of a given day) plus the CZK-pivot mechanism for cross-currency pairs. It is distinguishable from get_rate by framing the operation as amount conversion, though it never names the sibling explicitly.

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 wording — use this when you need a converted value rather than a raw rate. There is no explicit statement of when to prefer this over get_rate or how unsupported currencies behave, so the agent must infer the boundary.

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