Skip to main content
Glama

Nbp Pl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Currency Rate

currency_rate
Read-onlyIdempotent

PLN exchange rate for one currency over time. Specify the table (A/B for mid-rate, C for bid/ask) and a 3-letter ISO 4217 code (e.g. USD, EUR, GBP, CHF, JPY). Defaults to the latest rate; optionally pass a single date, last_n recent points, or a start_date/end_date window (max ~93 days, working days only). Use this for one currency; use exchange_rate_table for the whole list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesISO 4217 currency code, e.g. "USD", "EUR", "GBP".
dateNoSingle date, YYYY-MM-DD. Must be a working day or it 404s.
tableNoTable letter: "A" or "B" (mid-rate) or "C" (bid/ask). Default "A".
last_nNoReturn the N most recent rates. Ignored if date or start_date is given.
end_dateNoWindow end, YYYY-MM-DD. Used with start_date.
start_dateNoWindow start, YYYY-MM-DD. Pair with end_date. Max range ~93 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "code": "USD"
+  },
+  {
+    "code": "EUR",
+    "end_date": "2026-05-29",
+    "start_date": "2026-05-20",
+    "table": "A"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds constraints like 'max ~93 days, working days only', 'bid/ask for table C', and default behavior (latest rate). No contradiction.

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?

Single paragraph, front-loaded with main purpose, no redundant sentences. Every sentence provides essential information. Efficient and clear.

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 6 parameters with full schema coverage and no output schema, the description adequately explains all invocation patterns, constraints, and differs from sibling. An AI agent can correctly select and use this 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?

Input schema covers all parameters (100% coverage). Description adds practical details beyond schema: maximum date range, working days constraint, and meaning of table C (bid/ask). Enhances understanding.

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 PLN exchange rates for a single currency over time, specifies the verb and resource, and explicitly distinguishes from sibling 'exchange_rate_table' which returns the whole list.

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 'Use this for one currency; use exchange_rate_table for the whole list.' Also details when to use different parameters (latest, date, last_n, date range), providing clear 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