Skip to main content
Glama

finwire.pl - Polish financial data

Average new deposit and consumer loan rates in Polish banks (NBP MIR)

get_deposit_bank_average
Read-onlyIdempotent

Use for the average rate on new deposits in Polish banks by maturity, how much more the best deposits pay than the bank average, and the average rate and APRC of new consumer loans. For offers of single banks, use get_bank_rates. NBP interest rate statistics (MIR) for new household business in PLN: average rate on new term deposits (all maturities and by original maturity) with the value and share of new deposits by maturity, and the average rate and APRC (RRSO) of new consumer loans. With Premia za wybór lokaty finwire (finwire_deposit_choice_premium): how much more the finwire deposit index (5 best 3-month deposits) pays than the average new 1-3 month deposit, in pp and in PLN per year on PLN 10,000 after tax, plus a current estimate. Market averages, not an offer. Informational data, not investment advice.

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

Input Schema

NameRequiredDescriptionDefault
historyNoNumber of past months in the summary, default 12.

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.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, and the description adds genuinely new context: the NBP MIR data source, PLN household scope, what the premium calculation measures (pp and PLN/year on PLN 10,000 after tax), and an informational-not-advice disclaimer. It does not discuss freshness/lag of the 'current estimate' or pagination, but the safety and scope picture is well covered.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The routing sentence is correctly front-loaded and the disclaimer closes cleanly, but the body repeats itself: the deposit-rate scope is stated in the first sentence and restated in the 'NBP interest rate statistics (MIR)...' sentence. Trimming that duplication would sharpen an otherwise well-organized definition.

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?

An output schema exists, so return values need not be explained, and the description covers units, source, scope, and the sibling alternative. The only gap is the silent history parameter, which is left entirely to the schema for a tool whose summary window meaningfully changes the answer.

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% and the single 'history' parameter is documented in the schema as the number of past months with a default of 12. The description never mentions the lookback 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 the exact resource and metrics: average rate on new term deposits in Polish banks by maturity, the premium of the best deposits over the bank average, and the average rate/APRC of new consumer loans. It also names the source (NBP MIR) and currency (PLN), so an agent can tell precisely what data comes back and how it differs from bank-level rate tools.

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 'Use for...' trigger and routes the agent away with 'For offers of single banks, use get_bank_rates.' It further clarifies that the output is market averages rather than an offer, which tells the agent when this tool is inappropriate for a single-bank quote request.

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.