Skip to main content
Glama

Bnr Ro

by io.github.pipeworx-io

Bnr Exchange Rates History

bnr_exchange_rates_history
Read-onlyIdempotent

Historical National Bank of Romania (BNR) official FX reference rates, parsed from XML. With no arguments (or period="10days") returns the last 10 published business days. Pass year=YYYY (e.g. 2024) to return every published day in that calendar year. Returns an array of daily entries, each { date, rates:[{currency, value, multiplier}] }. Each rate is RON per multiplier units of the currency; per-1-unit rate = value / multiplier. Currencies are ISO 4217 codes. Note the currency set can vary across dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearNoCalendar year, e.g. 2024. Returns the full-year file for that year.
periodNoUse "10days" for the last 10 business days (default). Ignored if year is set.

TDQS

A4.6/5.0
Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive behavior. The description adds context about parsing XML, the return structure (array of daily entries), the rate calculation formula, and that the currency set varies across dates. No contradictions with annotations.

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 five sentences, front-loaded with purpose, then behavior, then return format, then rate explanation, then note on currency variation. Every sentence adds value without redundancy.

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 no output schema, the description thoroughly explains the return format (array of objects with date and rates array) and the rate calculation. It also notes that the currency set can vary, which is important for consumers. With only two optional parameters, the description covers all necessary context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for both parameters. The description adds clarity: explains default behavior (last 10 business days) and overrides (year ignored if year is set). It also provides examples of valid inputs.

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 the tool returns historical BNR FX rates, parsed from XML. It specifies the verb 'returns' and resource 'historical BNR rates', and the name 'bnr_exchange_rates_history' distinguishes it from the likely current-rate sibling 'bnr_exchange_rates'.

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 when to use no arguments or 'period=10days' for recent data, and when to use 'year=YYYY' for full-year data. It does not explicitly contrast with sibling tools, but the historical focus is clear.

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

All Bnr Ro toolsInspect
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.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but some overlap exists between ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim, which could cause confusion. However, the descriptions help clarify when to use each.

Naming Consistency3/5

Tool names use a mix of patterns (verb_noun, noun_noun, adjective_noun) but are consistently lowercase with underscores. Some names are vague like 'forever' and 'recent_alerts', but overall readable.

Tool Count3/5

32 tools is on the high side for a single server, but many are specialized and serve a broad data query platform. Some tools are meta-tools covering multiple use cases, which could reduce the need for so many.

Completeness4/5

The tool set covers a wide range of functionalities including data querying, entity resolution, comparisons, verification, memory, subscriptions, and prediction markets. Minor gaps like data export are not critical for its purpose.

Resources