Skip to main content
Glama
Sign In
cenogram-mcp-server

cenogram-mcp-server

Official
by cenogram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_price_statistics

Read-only

Get price-per-m² statistics for residential apartments by Polish location, using notarial-deed data over the last 24 months or full history; use search_transactions for other property types.

Instructions

Price per m² statistics for residential apartments (lokale mieszkalne) 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. 'Warszawa'/'Kraków'/'Łódź' auto-expand to all sub-districts; other names use partial match. Based on notarial-deed prices, not asking prices; coverage varies by county (some have data gaps of 5+ years).

Input Schema

NameRequiredDescriptionDefault
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. Changed4 schema fields changedv0.18.0
    • 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"
+}
    • 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."
    • 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"
+}
  2. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it as a safe read-only operation, but the description adds material context: data are based on notarial-deed prices rather than asking prices, county coverage varies with possible 5+ year gaps, and the response states the period used. These are meaningful behavioral caveats beyond the annotations.

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?

The description is compact and front-loaded: purpose and sibling exclusion come first, followed by window defaults, location matching, and data caveats. Every sentence contributes useful information without repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Input behavior and data caveats are well covered, but there is no output schema and the description does not explain what statistics are returned (e.g., median, average, count, breakdown). For an agent invoking a statistics tool, that return-shape gap leaves meaningful uncertainty.

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%, so all four parameters are already documented in the schema. The description reinforces the default window and location expansion behavior but adds little parameter semantics beyond what the schema provides, so the baseline of 3 is appropriate.

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 states a specific verb+resource: price per m² statistics for residential apartments by location. It also distinguishes the tool from search_transactions by naming the alternative for other property types.

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?

It clearly scopes usage to residential apartments and directs other property types to search_transactions. It also explains the default 24-month window and when to use period="all". However, it does not explicitly compare against related siblings like get_price_distribution or compare_locations.

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

Deploy Server

Other Tools