Skip to main content
Glama

Nbp Pl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Exchange Rate Table

exchange_rate_table
Read-onlyIdempotent

Full NBP exchange-rate table of PLN rates for many currencies at once. Pick a table: A = major currencies (mid-rate), B = other/minor currencies (mid-rate), C = bid/ask trading rates for the major set. Rates are PLN per 1 unit of each currency (per 100 for some minor units). Defaults to the latest published table; optionally pass a single date (YYYY-MM-DD) or last_n for the N most recent tables. Weekends/Polish holidays have no data (404).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSingle publication date, YYYY-MM-DD, e.g. "2026-05-29". Must be a working day or it 404s.
tableNoTable letter: "A" (major mid), "B" (other mid), or "C" (bid/ask). Default "A".
last_nNoReturn the N most recent tables instead of just today. Ignored if date is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "table": "A"
+  },
+  {
+    "last_n": 5,
+    "table": "C"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by specifying the rate format (PLN per unit, per 100 for some minors) and the 404 error condition on non-working days. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph of about 6 sentences, front-loading the main purpose. It is efficient with no fluff, though could be slightly more compact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 covers purpose, parameter behavior, and error conditions. It omits the exact return format (e.g., list of currency codes) but is sufficiently complete for a straightforward data retrieval 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%, but the description adds clarity: defaults to latest, last_n ignored if date provided, and explains table letters. This goes beyond the schema's property descriptions.

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 provides NBP exchange-rate tables with PLN rates for many currencies. It distinguishes between table types A, B, C and mentions options like date and last_n. The purpose is specific and differentiated from sibling tools like currency_rate.

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 each table type (A for major, B for other, C for bid/ask) and warns about 404 on holidays/weekends. However, it does not explicitly compare against sibling tools like currency_rate for single-currency queries, which would improve guidance.

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

All Nbp Pl 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