deweloperuch-mcp

Statystyki rynku miasta

get_market_statistics

Read-only

Retrieves city-level new-build market statistics—offer, investment and developer counts, price, price-per-m² and area distributions, and top developers—with optional price and area filters.

Instructions

Zwraca statystyki rynku ofert deweloperskich w jednym mieście: liczbę ofert, inwestycji i deweloperów, rozkład cen (PLN), cen za m² (PLN/m²) i metraży (m²) jako min, p25, median, p75 i max oraz największych deweloperów wg liczby ofert (developer_name, developer_slug, offers, investments, median_price_per_m2, developer_url). Opcjonalnie tylko oferty z zakresu ceny i metrażu. Użyj, gdy pytanie dotyczy rynku miasta (typowe ceny, kto ma najwięcej ofert), a nie konkretnych mieszkań (search_offers; inwestycje dewelopera daje get_developer).

Ograniczenia: tylko aktywne oferty (bez archiwalnych) i tylko jedno miasto (city_slug z search_locations; polska nie działa). Liczby to stan na dzień z pola wyniku as_of i mogą się nieco różnić od total w search_offers. Pojedynczych ofert tu nie ma: list_url to lista tych ofert na deweloperuch.pl z tymi samymi filtrami, a developer_url profil dewelopera: podawaj je użytkownikowi jako linki.

Input Schema

Name	Required	Description
`city`	Yes	city_slug jednego miasta z search_locations, np. krakow (nie polska).
`area_max`	No	Największy metraż w m².
`area_min`	No	Najmniejszy metraż w m².
`price_max`	No	Najwyższa cena oferty w PLN.
`price_min`	No	Najniższa cena oferty w PLN.
`top_developers`	No	Ilu największych deweloperów pokazać, 1–30, domyślnie 10.

Output Schema

Name	Required	Description
`hint`	No
`as_of`	No	Dzień, na który serwis podał oferty (może być wczorajszy): podawaj go przy liczbach.
`price`	No	Ceny w PLN: min, kwartyle, mediana, max.
`offers`	Yes	Pasujące aktywne oferty.
`area_m2`	No	Metraże w m².
`list_url`	No	Lista tych ofert na deweloperuch.pl (te same filtry ceny i metrażu): podaj ją użytkownikowi jako link.
`city_slug`	Yes
`truncated`	Yes	true: deweloperów jest więcej niż w top_developers.
`developers`	Yes	Wszyscy deweloperzy z pasującymi ofertami.
`investments`	Yes	Inwestycje z pasującymi ofertami.
`price_per_m2`	No	Ceny za m² w PLN.
`top_developers`	Yes	Deweloperzy z największą liczbą pasujących ofert, malejąco.
`developers_omitted`	Yes
`developers_returned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.0Nov 5, 2026

addedOutput schema / $defs / DeveloperShareItem / properties / developer_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Nazwa dewelopera.",
+  "title": "Developer Name"
+}

changedOutput schema / $defs / DeveloperShareItem / properties / developer_slug / description

Previous value: -"Identyfikator dewelopera (bez nazwy); nazwę i inwestycje daje get_developer."New value: +"Identyfikator dewelopera: inwestycje i ceny daje get_developer (city = city_slug wyniku)."

addedOutput schema / properties / as_of

Added value: +{
+  "anyOf": [
+    {
+      "format": "date",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Dzień, na który serwis podał oferty (może być wczorajszy): podawaj go przy liczbach.",
+  "title": "As Of"
+}

addedOutput schema / properties / investments / description
```
Added value: +"Inwestycje z pasującymi ofertami."
```

First observedv0.1.3Oct 16, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantially more: only active (non-archived) offers are counted, only one city per call, "polska" fails, figures are as-of the as_of result field and may diverge from search_offers totals, and individual offers are absent so list_url/developer_url must be surfaced to the user as links. These are real behavioral traits an annotation cannot convey.

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 purpose and outputs, then usage routing, then caveats — a sensible ordering. It is dense and the enumeration of every developer field is somewhat verbose, and "Opcjonalnie tylko oferty z zakresu ceny i metrażu" partly restates optional schema defaults, but no sentence is pure filler.

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?

For a read-only statistics tool with 6 params, full schema coverage and an output schema, the description covers scope, freshness, aggregation caveats, and the follow-up links an agent must present. Nothing needed to call it correctly — or to interpret the numbers — 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 description coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: city must be a city_slug obtained from search_locations and must not be "polska", and the price/area parameters restrict which offers the statistics are computed over rather than just filtering output. The top_developers parameter's effect is only implied by the mention of "największych deweloperów wg liczby ofert".

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?

Opens with a specific verb+resource ("Zwraca statystyki rynku ofert deweloperskich w jednym mieście") and enumerates exactly what is returned: offer/investment/developer counts, price and price-per-m² and area distributions as min/p25/median/p75/max, and top developers by offer count. It then explicitly contrasts itself with search_offers (individual listings) and get_developer (a developer's investments), so the agent can distinguish it from siblings 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?

Provides an explicit when-to-use rule — "Użyj, gdy pytanie dotyczy rynku miasta (typowe ceny, kto ma najwięcej ofert)" — together with the when-not condition ("a nie konkretnych mieszkań") and the exact alternative to route to (search_offers, get_developer). The single-city constraint and the warning that "polska" is not a valid city_slug further steer correct invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server