Skip to main content
Glama
Sign In

Cenogram - Polish Real Estate Data

by pl.cenogram.mcp
OverviewDiscussionsAdmin

get_price_statistics

Read-only

Price per m² statistics for residential apartments by location; for other property types use search_transactions. Default window: last 24 months (same as the search_transactions median); period="all" for full history. The response states the period used. Notarial-deed prices, not asking prices; coverage varies by county (some have data gaps of 5+ years).

Input Schema

NameRequiredDescriptionDefault
terytNoTERYT: 4 digits = county (1465 = Warszawa), 6 = Warszawa district (146505 = Mokotów). A gmina code is an error, unlike get_price_spread (narrows to county): pass the county. Wins over location.
dateToNoCustom window end, YYYY-MM-DD, inclusive (default today). Overrides period.
periodNoWindow: "24m" (default) = last 24 months, "all" = full history. Ignored when dateFrom or dateTo is set.
dateFromNoCustom window start, YYYY-MM-DD. Overrides period.
locationNoLocation name; 'Warszawa'/'Kraków'/'Łódź' expand to all sub-districts, other names use case-insensitive partial match (e.g. 'Wrocł' matches 'Wrocław'). Omit for all Poland.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / teryt
      Added value: +{
+  "description": "TERYT: 4 digits = county (1465 = Warszawa), 6 = Warszawa district (146505 = Mokotów). A gmina code is an error, unlike get_price_spread (narrows to county): pass the county. Wins over location.",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Filter by location name. 'Warszawa'/'Kraków'/'Łódź' auto-expand to all sub-districts. Other names use case-insensitive partial match (e.g. 'Wrocł' matches 'Wrocław'). Omit for all Poland."New value: +"Location name; 'Warszawa'/'Kraków'/'Łódź' expand to all sub-districts, other names use case-insensitive partial match (e.g. 'Wrocł' matches 'Wrocław'). Omit for all Poland."
  3. Changed3 schema fields changed
    • addedInput schema / properties / dateFrom
      Added value: +{
+  "description": "Custom window start, YYYY-MM-DD. Overrides period.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / dateTo
      Added value: +{
+  "description": "Custom window end, YYYY-MM-DD, inclusive (default today). Overrides period.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / period
      Added value: +{
+  "description": "Window: \"24m\" (default) = last 24 months, \"all\" = full history. Ignored when dateFrom or dateTo is set.",
+  "enum": [
+    "24m",
+    "all"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / location / description
      Previous value: -"Filter by location name (case-insensitive partial match). E.g. 'Kraków' matches 'Kraków-Podgórze', 'Kraków-Śródmieście', etc. Omit for all Poland."New value: +"Filter by location name. 'Warszawa'/'Kraków'/'Łódź' auto-expand to all sub-districts. Other names use case-insensitive partial match (e.g. 'Wrocł' matches 'Wrocław'). Omit for all Poland."
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, the description discloses substantive behavioral context: values are notarial-deed prices rather than asking prices, coverage varies by county with gaps of 5+ years, and the response self-reports the period used. It also pins the default window to the same 24 months used by search_transactions, which helps the agent keep comparisons consistent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three dense sentences with the primary purpose and sibling routing front-loaded, followed by default-window semantics and data-quality caveats. No filler, and every clause carries decision-relevant information.

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 no output schema, the description covers property-type scope, time window defaults, data source, and coverage caveats well. It never says which statistics are returned (median, mean, percentiles, sample counts) or the shape of the result, which is the one thing an agent would still have to guess.

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 carries detailed semantics (TERYT digit-length rules, date overrides, location expansion). The description reinforces only the period default and the period="all" option, adding little the schema does not already say, so 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?

States a specific resource and verb-phrase: price per m² statistics for residential apartments, scoped by location. It explicitly rules out other property types and routes them to search_transactions. It does not, however, distinguish itself from the two closest siblings, get_price_distribution and get_price_spread, which an agent could easily confuse with 'statistics'.

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?

Names one alternative explicitly ('for other property types use search_transactions') and gives a clear condition for choosing it. It also explains the default window and the period="all" option. The gap is that no guidance is given on when to prefer this tool over get_price_distribution or get_price_spread, the siblings with the most semantic overlap.

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

All Cenogram - Polish Real Estate Data toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources