Skip to main content
Glama

Официальные курсы валют ЦБ РФ

cbr_rates
Read-onlyIdempotent

Fetch official Bank of Russia exchange rates for a given date. Specify ISO currency codes for accounting or invoices.

Instructions

Официальные курсы валют Банка России на одну дату. Используйте, когда нужен курс на конкретный день (для счёта, проводки, отчёта); динамику за период даёт cbr_rate_history, пересчёт суммы — currency_convert. Возвращает date (на какую дату ЦБ установил курс — в выходные это последний рабочий день) и rates: code, name, nominal, value_rub (за номинал) и per_unit_rub (за 1 единицу — используйте его для расчётов); missing — запрошенные коды, которых нет у ЦБ. Без codes вернёт все ~50 валют, поэтому лучше передавать нужные коды. Источник cbr.ru, без токена, ответы кэшируются на час; только чтение.

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

Input Schema

NameRequiredDescriptionDefault
dateNoДата курса ГГГГ-ММ-ДД; по умолчанию сегодня
codesNoКоды валют ISO, например ["USD","EUR","CNY"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • changedInput schema / properties / date / description
      Previous value: -"Дата в формате ГГГГ-ММ-ДД"New value: +"Дата курса ГГГГ-ММ-ДД; по умолчанию сегодня"
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld, so safety is covered. The description still adds real operational context: source cbr.ru, no token required, one-hour response caching, and the weekend/holiday behavior (date falls back to the last working day). However, it does not describe error or rate-limit behavior.

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?

Front-loads purpose, then alternatives, then return shape and operational notes in a logical order. Dense and information-rich, though slightly run-on with several clauses packed into single sentences.

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

Completeness5/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 carries the return-value burden and does so: it enumerates date, rates (code, name, nominal, value_rub, per_unit_rub) and missing. Combined with the usage routing, an agent has everything needed to call it correctly.

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 the baseline is 3. The description goes beyond the schema by explaining that omitting codes returns all ~50 currencies and that passing explicit codes is preferred, plus the per_unit_rub vs value_rub distinction for calculations.

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+resource+scope: official CBR exchange rates for a single date. It explicitly names the two siblings it is not (cbr_rate_history for dynamics, currency_convert for conversion), so an agent can disambiguate without opening any schema.

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

Usage Guidelines5/5

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

Gives concrete when-to-use triggers (invoice, posting, report needing a rate for one specific day) and names the alternatives with the condition that selects them. Both exclusions and routing are explicit.

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