Skip to main content
Glama

finwire.pl - Polish financial data

NBP interest rates

get_interest_rates
Read-onlyIdempotent

Use for NBP policy rates. For bank offers, use get_bank_rates. Current NBP policy rates (reference, lombard, deposit, rediscount, discount) with the date of the last change, or the history of one rate. WIBOR and POLSTR are not available (GPW Benchmark license).

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_interest_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHistory window in days, default 365.
rateNoRate id for history, e.g. "stopa-referencyjna". Omit for all current rates.

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. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive and closed-world behavior, so the bar is lower; the description still adds real value by disclosing the licensing restriction that makes WIBOR/POLSTR unavailable and by stating that current rates come with a last-change date. It does not discuss history-window limits or result ordering, but the output schema covers return shape.

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?

Three short sentences: routing, content, then exclusion. The usage rule and the sibling hand-off are front-loaded, and no sentence is 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 rich annotations, an output schema, and fully documented parameters, the description's remaining burden is scope and data availability, both of which it covers precisely. Nothing an agent needs to invoke this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, including the 'stopa-referencyjna' example and the 365-day default. The description only implies the rate parameter via 'history of one rate' and says nothing about the days window, so it adds no meaning beyond the schema. Baseline 3 applies.

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 verb-and-resource pair (NBP policy rates) and enumerates the exact rate families returned (reference, lombard, deposit, rediscount, discount), plus the two modes: all current rates with last-change dates, or the history of a single rate. This is enough to distinguish it from get_bank_rates without opening 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?

It opens with an explicit selection rule ('Use for NBP policy rates'), routes the competing case to a named sibling ('For bank offers, use get_bank_rates'), and closes with an exclusion ('WIBOR and POLSTR are not available'). Both the positive and negative scope are stated, so an agent will not waste a call on unavailable series.

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.