Skip to main content
Glama

Nbu Ua

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Nbu Currency Rate

nbu_currency_rate
Read-onlyIdempotent

Official NBU rate for a SINGLE currency on one day. Pass valcode as an ISO-4217 code (e.g. USD, EUR, GBP). rate is UAH per 1 unit of that currency. Omit date for today. For a time series of one currency across a date range, use nbu_currency_history instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDay to fetch, format YYYYMMDD, e.g. "20240115". Omit for the latest/today.
valcodeYesISO-4217 currency code, e.g. "USD", "EUR", "PLN".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "valcode": "USD"
+  },
+  {
+    "date": "20240115",
+    "valcode": "EUR"
+  }
+]
  2. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds useful context (rate is UAH per 1 unit, omitting date gives today's rate) without repeating annotations. This adds value but annotations already cover safety aspects.

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?

Three sentences, concise and front-loaded with purpose. No unnecessary words. Every sentence adds useful information.

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?

Complete for a simple lookup tool. Covers usage, parameters, alternative, and return value semantics (UAH per unit). No output schema but enough context for an agent.

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% (both parameters described). The description adds meaning: explains date can be omitted for today, valcode should be ISO-4217 code, and clarifies rate units. This adds value beyond 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?

Description clearly states it provides the 'Official NBU rate for a SINGLE currency on one day', specifying the verb (query) and resource (currency rate). It distinguishes from the sibling tool nbu_currency_history.

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?

Explicitly says when to use this tool (single currency, one day) and when to use the alternative (nbu_currency_history for time series). Provides parameter hints like omitting date for today and using ISO-4217 code for valcode.

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