Skip to main content
Glama

Ключевая ставка ЦБ РФ

cbr_key_rate
Read-onlyIdempotent

Retrieve the Bank of Russia key rate, its current percentage, effective date, and change history for a period to answer rate and dynamics questions.

Instructions

Ключевая ставка Банка России: current_pct (текущая), as_of, since (с какой даты действует) и changes — только даты, когда ставка менялась, за период (по умолчанию последние 2 года). Используйте для вопросов о ставке и её динамике; чтобы посчитать пени или проценты за просрочку, вызывайте сразу late_payment_penalty — он сам учитывает все изменения ставки. Источник — таблица ключевой ставки на 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_key_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoКонец периода (по умолчанию сегодня)
fromNoНачало периода (по умолчанию 2 года назад)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world behavior, yet the description adds genuinely new facts: source is the CBR key-rate table on cbr.ru, no token required, one-hour cache, and that 'changes' contains only dates when the rate actually changed. That is substantive disclosure beyond the annotations.

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-loaded with the resource and its return fields, then usage routing, then provenance — logical order with little waste. Three clause-heavy sentences are dense but each carries information; slight redundancy in re-explaining the 2-year default.

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?

No output schema exists, so the description's enumeration of return fields (current_pct, as_of, since, changes) is essential and largely sufficient. Source, caching, and auth facts round it out; the only missing piece is how it differs from the other CBR rate tools.

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 from/to are fully documented in the schema, and the description's 'по умолчанию последние 2 года' simply echoes the documented default. The field enumeration describes outputs rather than inputs, so it adds no input-side semantics; baseline 3 is appropriate.

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?

States a specific resource (ключевая ставка Банка России) and enumerates the returned fields (current_pct, as_of, since, changes), so the agent knows exactly what it gets. It does not, however, differentiate itself from the near-identical siblings cbr_rates and cbr_rate_history, which is the main clarity gap.

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 explicit when-to-use (questions about the rate and its dynamics) and routes penalty/interest calculations to late_payment_penalty, explaining why that sibling is preferred. It omits any guidance against cbr_rates / cbr_rate_history, leaving the most likely sibling confusion unresolved.

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