Skip to main content
Glama

Prawnet: Polish case law and legislation

Kurs średni NBP (tabela A)

kurs_nbp
Read-onlyIdempotent

Średni kurs waluty z tabeli A NBP (api.nbp.pl) na dzień: kurs w PLN za 1 jednostkę, numer i data tabeli. Gdy tego dnia tabeli nie ma (weekend, święto, przed publikacją ok. 12:00) — z ostatniej wcześniejszej tabeli (tabela_z_dnia = false). kurs_z_dnia_poprzedzajacego = kurs z ostatniej tabeli przed tym dniem, czyli z ostatniego dnia roboczego przed dniem zdarzenia (m.in. art. 31a ust. 1 ustawy o VAT, art. 11a ust. 1 ustawy o PIT). Tabela A: ok. 30 walut (EUR, USD, CHF, GBP, JPY, CZK, DKK, NOK, SEK, HUF, UAH, CNY i in.); archiwum od 2002-01-02. Pole zrodlo: adres zapytania do API NBP i strona tabel. Bufor: dni minione do 30 dni, dzień bieżący do 30 minut.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "waluta": "<waluta>"
    },
    "name": "kurs_nbp"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoRRRR-MM-DD (także DD.MM.RRRR), od 2002-01-02; pominięte = dziś
walutaYesKod ISO 4217 z tabeli A NBP ("EUR", "chf") albo nazwa ("euro", "frank szwajcarski")

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: discloses the fallback-to-previous-table behavior, the tabela_z_dnia=false flag, the meaning of kurs_z_dnia_poprzedzajacego, the source field, and caching windows (30 days past, 30 minutes current day). This is exactly the behavioral context an agent needs.

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?

Front-loads the core definition, then layers fallback and legal context. Dense but every clause carries information; the legal citations are slightly heavy but justify the previous-day semantics.

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?

For a two-parameter read tool with an output schema, the description covers fallback logic, field meanings, currency scope, archive range, and caching. Nothing an agent needs to call it correctly is missing.

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%, so baseline is 3, but the description adds value: it notes the archive starts 2002-01-02 and that waluta accepts either ISO codes or Polish names, plus lists the ~30 covered currencies. That meaningfully enriches the waluta parameter.

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?

States a specific resource (average NBP table A rate) with the exact semantics: PLN per 1 unit, table number and date. No sibling tool deals with currency, so the scope is unambiguous.

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?

Explains the fallback condition precisely (weekend, holiday, before ~12:00 publication) and ties the previous-day rate to concrete legal use cases (VAT art. 31a, PIT art. 11a). No explicit when-not guidance, but no competing sibling exists to route away from.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources