Skip to main content
Glama

finwire.pl - Polish financial data

Statutory interest rates

get_statutory_interest
Read-onlyIdempotent

Use for statutory, late payment, maximum, tax arrears and B2B invoice interest rates in Poland. For NBP rates only, use get_interest_rates. Polish interest rates set by law from NBP rates: statutory (capital) and late payment interest (Civil Code), maximum interest, interest on tax arrears with the reduced rate (Tax Ordinance), late payment interest in commercial transactions (B2B invoices). Each rate has the date from which it applies and the next rate (announced after an RPP decision, or the B2B rate for the next half-year: settled or a finwire.pl estimate).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_statutory_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
urlYes
asOfNo
dataNo
titleYes
sourceYes
docsUrlYes
licenseYes
summaryYes
citationYes
datasetIdYes
sourceUrlNo
truncatedNo
serverDateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context: each rate carries an applicability date and a 'next rate' value that may be settled or a finwire.pl estimate following an RPP decision — useful data-provenance information an agent would not get from the annotations. It stops short of describing volume or update cadence, keeping it just below 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.

Conciseness4/5

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

The routing instruction and alternative are front-loaded in the first two sentences, which is the right structure. The third sentence is a dense, list-heavy explanation of the data categories and the trailing parenthetical about the 'next rate' is somewhat crowded, but every clause carries information rather than filler.

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?

With no input parameters, full annotation coverage, and an output schema that handles return values, the remaining burden is scope and routing — both are handled precisely, including the legal sources and the estimate caveat. An agent has everything needed to decide to call this tool and to interpret the 'next rate' field.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not waste space inventing parameter discussion.

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 names a specific resource (Polish statutory/late payment/maximum/tax arrears/B2B interest rates) and enumerates the exact legal bases (Civil Code, Tax Ordinance, commercial transactions). It also explicitly distinguishes itself from get_interest_rates, so an agent can route without inspecting either schema.

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?

The first sentence gives a direct 'use for' instruction with the covered rate categories, and the second sentence names the alternative (get_interest_rates) plus the exact condition that selects it ('For NBP rates only'). Both the when-to-use and when-to-use-something-else are stated.

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.