TokenBel Financial Data

currency_rate_get

Read-onlyIdempotent

Get NBRB (National Bank of Belarus) official FX rates against BYN (Belarusian ruble) for USD, EUR, and/or RUB. Rates are BYN per 1 unit of foreign currency. Modes: latest (no dates), single_date (date), range (date_from/date_to, either bound optional), or grouped weekly/monthly aggregates (group_by + range). Only usd/eur/rub are supported; BYN is the implicit base currency.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Single date in YYYY-MM-DD format. Mutually exclusive with date_from/date_to.
`date_to`	No	Range end date in YYYY-MM-DD format (inclusive, >= date_from). Open-ended or today-bounded ranges bypass cache.
`currency`	No	Filter to one supported foreign currency: usd, eur, or rub. Omit to return all three. BYN is the base currency, not a target.
`group_by`	No	Aggregate by week or month. Requires a date range (date_from/date_to), not a single date.
`date_from`	No	Range start date in YYYY-MM-DD format (inclusive). Can be omitted for open-start range.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`count`	Yes
`date_to`	Yes
`results`	Yes
`currency`	Yes
`group_by`	No
`date_from`	Yes
`base_currency`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds that rates are BYN per 1 unit, only usd/eur/rub are supported, BYN is implicit base, and open-ended or today-bounded ranges bypass cache. These behavioral details go beyond annotations and provide useful operational context.

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?

The description is two concise sentences with no redundant words. It front-loads the core purpose and then lists modes and constraints efficiently. Every word earns its place.

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?

Given the presence of an output schema (not shown but known), rich annotations, and clear parameter constraints, the description is complete. It covers all usage modes, supported currencies, cache behavior, and base currency. No additional information is needed for correct invocation.

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 baseline is 3. The description adds value by clarifying mutual exclusivity of date vs date_from/date_to, that group_by requires a range, and that open-ended ranges bypass cache. It also reinforces currency filtering and base currency. This extra context aids parameter selection.

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 retrieves NBRB official FX rates against BYN for USD, EUR, and RUB. It specifies the exchange rate format and distinguishes from sibling tools (none of which are FX rate tools). The verb 'get' combined with resource 'NBRB official FX rates' is specific and unambiguous.

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?

The description explains four modes (latest, single_date, range, grouped weekly/monthly) and which parameters activate them. It implicitly guides when to use each, but does not explicitly state when not to use or compare to alternatives. However, the context is clear enough for agent decision-making.

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

All TokenBel Financial Data tools Inspect

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.4/5.0

Disambiguation5/5

Each tool targets a distinct entity or operation: bonds, shares, tokens, companies, issuers, currency rates, news, and searches. No two tools have overlapping purposes; even similar tools like bond_list and company_bonds_list are clearly differentiated by scope (global vs per-company).

Naming Consistency4/5

Tools mostly follow a pattern of entity_noun + verb (e.g., bond_list, share_get_by_uuid, company_bonds_list). Some exceptions like currency_rate_get and entity_news_list place the verb at the end, but the pattern is predictable and readable.

Tool Count5/5

With 19 tools covering bonds, shares, tokens, companies, issuers, currency rates, news, and trading statistics, the number is well-calibrated to the domain. Each tool serves a clear purpose without redundancy.

Completeness5/5

The tool surface provides comprehensive read access to the financial data domain: search, retrieval, listing with filters, trading statistics, and news. All expected query operations are present, and no obvious gaps are apparent for a data provider.

Resources

Need Help?