Skip to main content
Glama

Nbp Pl

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Gold Price

gold_price
Read-onlyIdempotent

NBP accounting price of gold (cena złota): PLN per 1 gram of pure gold (1000 fineness). Defaults to the latest published price; optionally pass a single date, last_n recent points, or a start_date/end_date window (max ~93 days, working days only). Weekends/Polish holidays have no data (404).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoSingle date, YYYY-MM-DD. Must be a working day or it 404s.
last_nNoReturn the N most recent prices. 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: +[
+  {},
+  {
+    "last_n": 10
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context about data availability (404 for weekends/holidays) and constraints (max window length, working days only), which goes beyond 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 two sentences that front-load the core purpose and then detail usage modes and constraints. Every sentence provides necessary information without redundancy, making it highly efficient.

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 the absence of an output schema, the description mentions the unit and purity but does not specify the exact return structure (e.g., date-price pairs). However, the coverage of input modes and constraints is sufficient for basic usage, leaving minor gaps.

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?

With 100% schema coverage, the schema already documents parameters concisely. The description adds value by explaining default behavior, parameter interactions (last_n ignored if date/start_date given), and the working days constraint, improving semantic 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 the tool retrieves the NBP accounting price of gold in PLN per gram of pure gold, with specific unit and fineness. It distinguishes itself by specifying the source and default behavior, though no direct sibling for gold price exists.

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 elaborates on when to use each parameter: default latest, single date, last_n points, or date window with a max range of ~93 working days. It also notes when data is unavailable (weekends/holidays). No explicit alternatives are given, but usage modes are clear.

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