Skip to main content
Glama

Nbu Ua

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Nbu Currency History

nbu_currency_history
Read-onlyIdempotent

Daily time series of the official NBU rate for ONE currency over a date range. Pass valcode (ISO-4217, e.g. USD) and start/end as YYYYMMDD. Returns one record per business day: {exchangedate (DD.MM.YYYY), cc, txt (Ukrainian name), enname (English name), rate (UAH per units), units, rate_per_unit}. Omit valcode to get every currency over the range. Newest first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesRange end, YYYYMMDD, e.g. "20240131".
startYesRange start, YYYYMMDD, e.g. "20240101".
valcodeNoISO-4217 currency code, e.g. "USD". Omit to return all currencies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "end": "20240131",
+    "start": "20240101",
+    "valcode": "USD"
+  },
+  {
+    "end": "20231231",
+    "start": "20231201"
+  }
+]
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnly, openWorld, idempotent, and non-destructive. Description adds valuable behavioral details: returns one record per business day, field formats (e.g., exchangedate in DD.MM.YYYY), ordering (newest first). 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?

Two sentences plus a list of fields. Every sentence is informative. Front-loaded with purpose. No verbosity or 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 the input schema (3 params, 2 required) and no output schema, the description fully covers the return structure. The simplicity of the tool means this is complete for an agent to use correctly.

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 has 100% coverage with descriptions, but the description further clarifies with examples (e.g., YYYYMMDD format, ISO-4217 codes) and details the returned fields. Provides examples in the schema. Adds significant value beyond bare 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?

Description clearly states it provides daily time series for one currency (or all) over a date range, with specific verb and resource. It distinguishes from siblings like nbu_currency_rate by noting the time series aspect and the option to omit valcode for all currencies.

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?

Explicitly says to pass valcode for a single currency or omit for all, with start/end in YYYYMMDD format. Provides examples in the schema. Does not explicitly state when not to use, but the context is clear enough for the agent.

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

All Nbu Ua toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources