Skip to main content
Glama

finwire.pl - Polish financial data

Flat prices per m² (notarial deeds)

get_housing_prices
Read-onlyIdempotent

Use for flat prices per m2 in a city or district. Transaction prices of flats per square meter from notarial deeds (RCN): median, quartiles, year-over-year change and number of deeds in 17 cities, or per district of one city. source "gus" gives the GUS quarterly series instead. view "location-premium" gives finwire_location_premium: per district, how far the actual price deviates from the price expected from neighbourhood quality (transport, schools, shops, greenery, quiet, air), with model fit and accuracy; without city, the status of every city. The quarterly finwire indices finwire_rcn_price_index and finwire_price_gap_index: get_finwire_index.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug (e.g. "Kraków" or "krakow") for its districts; omit for all cities.
viewNoprices (default) or location-premium.
sourceNorcn (default, notarial deeds) or gus.
districtNoFilter districts by name, e.g. "Mokotów".

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 / view
      Added value: +{
      +  "description": "prices (default) or location-premium.",
      +  "enum": [
      +    "prices",
      +    "location-premium"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/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 closed-world, so the safety profile is covered. The description adds value beyond that by disclosing data provenance (notarial deeds), coverage breadth (17 cities), and what the location-premium view actually computes (deviation from expected price given transport, schools, shops, greenery, quiet, air, plus model fit and accuracy). It stops short of any latency, freshness, or permission notes, which keeps it at a 4.

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?

It is dense and front-loaded with the core purpose, but the later sentences are grammatically loose and compressed ("view \"location-premium\" gives finwire_location_premium: per district, how far...", "The quarterly finwire indices ...: get_finwire_index."), forcing the reader to parse fragments. The information is worth keeping, but the packaging could be cleaner.

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 described, and the description already covers the two views, the two sources, and geographic scope. What remains thin is how district behaves when city is omitted and whether district works across the location-premium view, a small but real gap for a 4-parameter tool.

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 genuinely enriches two parameters the schema only labels: it explains what the "location-premium" view yields beyond the enum name, and what source "gus" substitutes for the default. District is left to the schema with no extra guidance, which is the only shortfall.

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 opening sentence names a specific verb+resource (flat prices per m2 in a city or district), and the description goes on to enumerate the concrete measures returned (median, quartiles, year-over-year change, deed counts) plus coverage (17 cities, or districts of one city). It also explicitly separates itself from the GUS quarterly series and from the finwire indices, so an agent can distinguish it from siblings without opening a 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?

Explicit routing is given for each alternative: default RCN notarial deeds, source "gus" for the GUS quarterly series, view "location-premium" for the quality-adjusted deviation view, and get_finwire_index for the quarterly finwire indices. The description even states that omitting city in the location-premium view returns the status of every city, which is the key usage nuance.

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.