Skip to main content
Glama

finwire.pl - Polish financial data

Market rates: loans, deposits, bonds

get_bank_rates
Read-onlyIdempotent

Use for market rates of mortgages, cash loans, deposits, savings accounts and retail bonds. For NBP rates, use get_interest_rates. Aggregates of offers currently on the market (median and percentiles, no single bank offers): mortgage APRC and margin, cash loan APRC, term deposit and savings account rates; or retail government bond rates (product "bonds"). finwire indices of the best offers (finwire_mortgage_barometer, finwire_deposit_rate_index, finwire_savings_rate_index, finwire_account_cost_index): get_finwire_index.

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": {
      "product": "<product>"
    },
    "name": "get_bank_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountNoModel amount in PLN.
periodNoMortgage: years; cash loan and deposit: months.
productYesProduct: mortgage, cash loan, term deposit, savings account or retail government bonds.

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. Changed1 schema field changed
    • addedInput schema / properties / product / description
      Added value: +"Product: mortgage, cash loan, term deposit, savings account or retail government bonds."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: these are aggregates (median and percentiles) of offers currently on the market with no single bank offering them, which tells the agent not to expect per-institution rows. It does not mention freshness/update cadence or any limits, 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.

Conciseness4/5

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

Front-loaded with the use case, then exclusions, then a compact enumeration of what aggregate categories are returned. It is dense and every clause carries information, though the long semicolon-chained sentence covering aggregation semantics and bond products is harder to scan than it needs to be.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile; what remains is the aggregate-vs-single-offer distinction, which is included. The only gap is that it never states whether amount and period are optional and what happens when they are omitted, which matters because only product is required.

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 each parameter already documents its meaning, range and units (amount in PLN, period interpreted as years for mortgage and months for loan/deposit). The description only restates the product categories and maps the bonds case, adding no unit or default semantics the schema lacks. Baseline 3 is appropriate when the schema carries the load.

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 verb+resource: market rates for mortgages, cash loans, deposits, savings accounts and retail bonds. It goes further and distinguishes scope from two siblings by name (get_interest_rates for NBP rates, get_finwire_index for finwire indices), so an agent can route without opening any 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 definition gives explicit positive scope (market aggregates of offers) and two explicit exclusions with the alternative tool names attached: NBP rates go to get_interest_rates, finwire barometers/indices go to get_finwire_index. It also lists the exact finwire index names so the agent can pattern-match a user request to the right sibling.

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.