Skip to main content
Glama

Kalkulator B2B

Kurs średni NBP do faktury w walucie

nbp_rate
Read-only

Kurs średni NBP (tabela A) z ostatniego dnia roboczego PRZED podaną datą — po nim przelicza się na złote przychód, koszt i VAT z faktury w walucie (art. 11a ustawy o PIT, art. 31a ustawy o VAT). Podaj walutę i datę zdarzenia (np. dzień wystawienia faktury); weekendy i święta narzędzie omija samo. Zwraca kurs, numer tabeli i jej datę — nie podawaj kursu z pamięci. Waluty spoza tabeli A nie są obsługiwane.

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": {
      "currency": "<currency>",
      "date": "<date>"
    },
    "name": "nbp_rate"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDzień zdarzenia (RRRR-MM-DD): wystawienia faktury, uzyskania przychodu, poniesienia kosztu albo powstania obowiązku VAT — NIE dzień wcześniej; kurs będzie z ostatniego dnia roboczego przed tą datą
currencyYesKod waluty ISO 4217 z tabeli A NBP, np. EUR, USD, GBP, CHF

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as a safe read (readOnlyHint=true, destructiveHint=false), yet the description still adds real behavior: weekends and holidays are skipped automatically, and the response carries the rate, the table number and the table's date. It also warns the agent not to supply a rate from memory. It omits failure behavior for invalid, future or pre-coverage dates, which keeps it from a 5.

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?

It is one dense paragraph, front-loaded with the definition and date rule, followed by usage, exclusions and a warning. Every clause carries information an agent needs, and nothing is repeated across sentences.

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, no-annotations-of-its-own read tool with no output schema, the definition is complete: it covers the selection rule, the date semantics, the return shape (rate, table number, table date) and the supported-currency boundary. An agent can call it correctly from the description alone.

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 the baseline is 3, but the description still reinforces the key semantic trap: the date is the event date, not the day before, and currency comes from the table A list. The invoice-issuance-date example adds a concrete usage anchor beyond the schema's field 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 definition names a specific resource (NBP mid rate, table A) and a precise selection rule: the last business day strictly before the supplied date. It also states its purpose — converting foreign-currency invoice revenue, cost and VAT into PLN — with the legal basis, so the agent can distinguish it from generic calculator or working-day siblings without opening the schema.

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?

It states when to use it (foreign-currency invoices; pass the date of the triggering event such as the invoice date) and gives an explicit exclusion: currencies outside table A are not supported. It does not, however, name a sibling tool to use instead for unsupported currencies or for other date lookups, so agents get context but no routing alternative.

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