Skip to main content
Glama
Sign In
ru-business-mcp

ru-business-mcp

by penmadebykisss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Пересчёт суммы по курсу ЦБ

currency_convert
Read-onlyIdempotent

Convert amounts between rubles and foreign currencies, or between currencies via ruble cross-rate, using the official Bank of Russia rate for a chosen date. Ideal for invoices, acts, and reports.

Instructions

Пересчитывает сумму по официальному курсу ЦБ РФ на дату: рубли ↔ валюта или валюта ↔ валюта (кросс-курс через рубль). Используйте для счетов, инвойсов, актов и отчётов, где нужен именно курс ЦБ; сам курс без суммы — cbr_rates, динамика — cbr_rate_history. Возвращает rate (сколько единиц to за 1 from), result (округлено до копеек) и rate_date — дату, на которую ЦБ установил курс (для выходных это предыдущий рабочий день). Без date — курс на сегодня. Коммерческие курсы банков не учитываются. Источник cbr.ru, без токена; только чтение.

Input Schema

NameRequiredDescriptionDefault
toYesЦелевая валюта
dateNoДата курса ГГГГ-ММ-ДД; по умолчанию сегодня
fromYesИсходная валюта (RUB, USD, EUR, CNY…)
amountYesСумма

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.9/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld), yet the description still adds substantive behavior: the returned fields (rate as units-of-to-per-from, result rounded to kopecks, rate_date), the weekend/holiday fallback to the previous business day, and the fact that no token is required and the source is cbr.ru.

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?

Front-loaded with the action and direction, then alternatives, then return values, then caveats. Dense but each sentence carries non-redundant information; no filler.

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 present, the description correctly absorbs the return-value explanation (rate/result/rate_date) plus rounding and weekend semantics. An agent has everything needed to call and interpret this tool.

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 slightly beyond the schema by explaining the cross-rate mechanism (через рубль) and the semantic meaning of the returned rate direction, though the date default ('по умолчанию сегодня') merely restates the schema.

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 opening clause states a specific verb and resource (пересчитывает сумму по курсу ЦБ) and immediately delimits scope: RUB↔валюта and cross-rate через рубль. It is trivially distinguishable from cbr_rates (rate only) and cbr_rate_history (dynamics), both of which it names explicitly.

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?

Names the target use cases (счета, инвойсы, акты, отчёты), routes the agent to two alternatives by condition (нужен только курс → cbr_rates; динамика → cbr_rate_history), and states an exclusion (коммерческие курсы банков не учитываются). Nothing is left to inference.

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

Deploy Server

Other Tools