Skip to main content
Glama

finwire.pl - Polish financial data

Parking space prices from developer price lists (dane.gov.pl)

get_parking_prices
Read-onlyIdempotent

Use for the price of a parking space, a garage space or a storage room from developers in a Polish city, and how it compares with the price of 1 m2 of a new flat. Say that these are asking prices from developer price lists and give the week. Asking prices of parking spaces sold by housing developers in Poland, from the daily price-list files on dane.gov.pl (act on transparency of new-flat prices). Weekly median, quartiles and counts of single parking spaces for Poland and cities above the publication threshold, underground or garage-hall vs outdoor vs garage, storage rooms and bike boxes, how many square metres of a new flat in the same city one space costs, change vs 4 weeks earlier and a weekly trend. Finwire index finwire_dev_parking_price.

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

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or slug (Warszawa, zielona-gora). Default: Poland with the city list.
weeksNoNumber of past weeks in the trend, 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

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behaviour, so the description's job is lighter and it still adds real value: data provenance (daily price-list files on dane.gov.pl), the legal basis, the fact that these are asking rather than transaction prices, and the statistical shape of the output (weekly median, quartiles, counts, 4-week change, trend, coverage threshold). It omits refresh cadence and lag beyond 'weekly', 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.

Conciseness3/5

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

Purpose is front-loaded, but the second sentence is a long comma-spliced enumeration of every statistic returned, and 'from developers in a Polish city' is restated as 'sold by housing developers in Poland'. It also embeds an instruction to the assistant ('Say that...') and an internal index name (finwire_dev_parking_price) that add length without helping selection.

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?

The definition covers purpose, provenance, price type caveat, and coverage rules, which is enough for a read-only two-parameter query tool with an output schema. It pads by enumerating return values the output schema already supplies, and leaves the relationship to the housing-price tool unstated, but nothing needed 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.

Parameters3/5

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

Schema coverage is 100%: 'city' already documents accepted names/slugs and the Poland default, and 'weeks' documents the trend window and default of 12. The description adds only the instruction to 'give the week', which is a presentation hint rather than added parameter meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific resource (parking space, garage space, storage room prices from developers in a Polish city) plus the comparison angle against 1 m2 of a new flat. It is clearly distinct from a generic housing-price tool. It does not name the sibling it complements or exclude (e.g. get_housing_prices), so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'Use for...' clause gives a when-to-use trigger, and the 'say that these are asking prices' line sets framing expectations. However, there is no when-not guidance, no stated prerequisites, and no routing to or away from the closely related housing-price sibling, so usage selection is only implied.

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.