Skip to main content
Glama

finwire.pl - Polish financial data

Price limits per m2 in the family housing loan (BGK)

get_rkm_price_limits
Read-onlyIdempotent

Use for the maximum price per m2 in the family housing loan without down payment (rodzinny kredyt mieszkaniowy, BGK guarantee) in a city or voivodeship, and to check if a flat qualifies. Give BGK as the source and the quarter. Maximum price per m2 of a flat that can be bought with the Polish family housing loan (rodzinny kredyt mieszkaniowy, "Mieszkanie bez wkładu własnego": mortgage without down payment, BGK guarantees the missing part), from the quarterly lists of Bank Gospodarstwa Krajowego based on voivode announcements. 52 locations: each voivodeship city, the municipalities bordering it and all other municipalities. Two limits: first buyer from the developer and secondary market or cooperative right. Gives change vs previous quarter and year, history, an optional check of a price per m2 against the limit, and the finwire index finwire_rkm_offer_fit (share of developer price-list flats in voivodeship cities within the limit). Attribution to BGK is mandatory (not CC BY).

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

Input Schema

NameRequiredDescriptionDefault
marketNoprimary = first buyer from the developer, secondary = previous owner or cooperative right. Default primary.
locationNoVoivodeship city (Kraków), voivodeship (małopolskie) or key (krakow, krakow-okolice, malopolskie-pozostale). Default: all voivodeship cities.
quartersNoNumber of past quarters in the history, default 4.
price_per_m2NoPrice per m2 in PLN to check against the limit of the first matching location.

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

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral context: quarterly publication cadence, the two limit categories, change-vs-previous-quarter/year and history, the finwire_rkm_offer_fit index, and the mandatory BGK attribution (not CC BY). The licensing/attribution requirement is especially valuable and is not available from any structured field.

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 core guidance is front-loaded, but the body is one long run-on that repeats itself – "rodzinny kredyt mieszkaniowy" and the BGK guarantee are explained twice, and multiple parenthetical glosses inflate length. It is readable but not tight.

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 an output schema present, return values need not be spelled out; the description still covers coverage scope, limit categories, history depth, the optional qualification check, and the attribution obligation. Nothing an agent needs in order to call it correctly is missing.

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 adds meaning beyond the schema: location can be a voivodeship city, a voivodeship, or a key, and the 52 locations include the voivodeship city plus bordering and remaining municipalities; it also explains that there are two distinct limit types keyed to market. That clarifies why the market enum exists.

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 (maximum price per m2 limits for the Polish family housing loan / rodzinny kredyt mieszkaniowy), its granularity (city or voivodeship, 52 locations), and its source (BGK quarterly lists). It also states the secondary job – checking whether a flat qualifies – so an agent can tell this apart from generic housing-price or legal-limit siblings.

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?

"Use for ... and to check if a flat qualifies" gives clear triggering contexts, including the optional price-against-limit check. There are no explicit exclusions or named alternatives (e.g. when to prefer get_housing_prices over this), so it falls short of a 5.

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.