Skip to main content
Glama
Sign In

cenaodhad – ceny bytů v Praze z katastru

by cz.cenaodhad
OverviewDiscussionsAdmin

Odhad ceny bytu / Apartment price estimate

odhad_ceny_bytu
Read-onlyIdempotent

CZ: Použij, když uživatel chce odhad ceny KONKRÉTNÍHO bytu v Praze a zná čtvrť a plochu v m². Vrátí střední odhad, rozpětí a Kč/m² z realizovaných prodejů podobně velkých bytů v katastru nemovitostí (ne z inzerátů). Orientační rozpětí, ne znalecký posudek. Nevyžaduje registraci ani kontaktní údaje. | Pravidlo: když uživatel neuvedl plochu, zeptej se na čtvrť (nebo ulici – tu převedeš na čtvrť přes ceny_bytu_lokalita) a plochu v m²; do té doby můžeš použít ceny_bytu_lokalita. Stačí čtvrť a plocha. Pokud uživatel sám uvede stav bytu nebo konstrukci domu, předej je (stav, konstrukce); vrátí se navíc orientační úprava upraveno_kc, střední odhad a rozpětí se nemění. Samostatně se na ně nedoptávej. Patro, výtah ani orientaci model nezohledňuje. | Nepoužívej, když uživatel už má nabídkovou cenu z inzerátu (→ overeni_ceny_inzeratu), když chce jen cenovou hladinu lokality bez plochy (→ ceny_bytu_lokalita) nebo porovnat lokality (→ srovnani_ctvrti). Rodinné domy → odhad_ceny_domu, pozemky → odhad_ceny_pozemku. Upřesnění ceny bytu (patro, dispozice) → konzultace_makler, jen pokud o to uživatel výslovně požádá. | EN: Use when the user wants a price estimate for a SPECIFIC Prague apartment and knows the district and floor area in m². Returns a mid estimate, range and CZK/m² from realised sales of similar-sized apartments in the Czech land registry (not listings). Indicative range, not an appraisal. Requires no sign-up or contact details. | Rule: if the user has not given the floor area, ask for the district (or street – map it to a district with ceny_bytu_lokalita) and the area in m²; until then you can use ceny_bytu_lokalita. District and floor area are enough. If the user mentions the apartment condition or the building construction on their own, pass them on (stav, konstrukce); the result then also includes an indicative adjustment upraveno_kc, the mid estimate and range do not change. Do not ask for them separately. The model does not use floor level, lift or orientation. | Do not use when the user already has an asking price from a listing (→ overeni_ceny_inzeratu), wants only the price level of a locality without an area (→ ceny_bytu_lokalita) or wants to compare localities (→ srovnani_ctvrti). Family houses → odhad_ceny_domu, land → odhad_ceny_pozemku. Refining an apartment price (floor, layout) → konzultace_makler, only if the user explicitly asks for it.

Input Schema

NameRequiredDescriptionDefault
stavNoNepovinné. Stav bytu, jen když ho uživatel sám uvedl; nedoptávej se. Hodnoty: "Dobrý", "Novostavba", "Po rekonstrukci", "Před rekonstrukcí", "Velmi dobrý". Střední odhad a rozpětí nemění, vrátí navíc orientační úpravu upraveno_kc / Optional. Apartment condition, only if the user mentioned it; do not ask for it. Values: "Novostavba" (new build), "Po rekonstrukci" (renovated), "Velmi dobrý" (very good), "Dobrý" (good), "Před rekonstrukcí" (needs renovation). Does not change the mid estimate or range; adds an indicative adjustment upraveno_kc
ctvrtYesNázev pražské čtvrtě (katastrální území), ne obvod „Praha N“ ani ulice; diakritika nevadí. Např. "Vinohrady", "Žižkov", "Nusle" / Prague district (cadastral area), not a "Praha N" borough or a street; diacritics optional. E.g. "Vinohrady", "Žižkov", "Nusle"
jazykNoJazyk odpovědi / Response languagecs
plocha_m2YesPodlahová plocha bytu v m² jako číslo, 15–250, např. 60 / Apartment floor area in m² as a number, 15–250, e.g. 60
konstrukceNoNepovinné. Konstrukce domu, jen když ji uživatel sám uvedl; nedoptávej se. Hodnoty: "Cihlová", "Panelová", "Smíšená". Střední odhad a rozpětí nemění, vrátí navíc orientační úpravu upraveno_kc / Optional. Building construction, only if the user mentioned it; do not ask for it. Values: "Cihlová" (brick), "Panelová" (prefab panel), "Smíšená" (mixed). Does not change the mid estimate or range; adds an indicative adjustment upraveno_kc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / konstrukce
      Added value: +{
+  "description": "Nepovinné. Konstrukce domu, jen když ji uživatel sám uvedl; nedoptávej se. Hodnoty: \"Cihlová\", \"Panelová\", \"Smíšená\". Střední odhad a rozpětí nemění, vrátí navíc orientační úpravu upraveno_kc / Optional. Building construction, only if the user mentioned it; do not ask for it. Values: \"Cihlová\" (brick), \"Panelová\" (prefab panel), \"Smíšená\" (mixed). Does not change the mid estimate or range; adds an indicative adjustment upraveno_kc",
+  "enum": [
+    "Cihlová",
+    "Panelová",
+    "Smíšená"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / stav
      Added value: +{
+  "description": "Nepovinné. Stav bytu, jen když ho uživatel sám uvedl; nedoptávej se. Hodnoty: \"Dobrý\", \"Novostavba\", \"Po rekonstrukci\", \"Před rekonstrukcí\", \"Velmi dobrý\". Střední odhad a rozpětí nemění, vrátí navíc orientační úpravu upraveno_kc / Optional. Apartment condition, only if the user mentioned it; do not ask for it. Values: \"Novostavba\" (new build), \"Po rekonstrukci\" (renovated), \"Velmi dobrý\" (very good), \"Dobrý\" (good), \"Před rekonstrukcí\" (needs renovation). Does not change the mid estimate or range; adds an indicative adjustment upraveno_kc",
+  "enum": [
+    "Dobrý",
+    "Novostavba",
+    "Po rekonstrukci",
+    "Před rekonstrukcí",
+    "Velmi dobrý"
+  ],
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / ctvrt / description
      Previous value: -"Název pražské čtvrtě (katastrální území), např. \"Vinohrady\" / Prague cadastral district, e.g. \"Vinohrady\""New value: +"Název pražské čtvrtě (katastrální území), ne obvod „Praha N“ ani ulice; diakritika nevadí. Např. \"Vinohrady\", \"Žižkov\", \"Nusle\" / Prague district (cadastral area), not a \"Praha N\" borough or a street; diacritics optional. E.g. \"Vinohrady\", \"Žižkov\", \"Nusle\""
    • changedInput schema / properties / plocha_m2 / description
      Previous value: -"Plocha bytu v m², rozsah 15–250 / Apartment area in m², range 15–250"New value: +"Podlahová plocha bytu v m² jako číslo, 15–250, např. 60 / Apartment floor area in m² as a number, 15–250, e.g. 60"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With readOnlyHint/idempotentHint already provided, the description still adds substantial context: the data source (land registry sales, not listings), that the figure is indicative rather than an appraisal, that no registration is needed, that the model ignores floor level/lift/orientation, and that stav/konstrukce leave the mid estimate unchanged but add upraveno_kc.

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?

Purpose is front-loaded and the rules are well ordered, but the fully bilingual CZ/EN mirror effectively doubles the length, making it longer than strictly necessary for a single consumer despite every clause being meaningful.

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?

Very complete for a no-output-schema tool: it explains what is returned (mid estimate, range, CZK/m², optional upraveno_kc), the data provenance, the limitations, and explicitly routes every adjacent case to the correct sibling tool.

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%, so the schema already documents ctvrt, plocha_m2, stav, konstrukce and jazyk. The description mainly reinforces the when-to-pass rule for stav/konstrukce that the schema already states, so baseline 3 applies with little added semantics beyond structured fields.

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 precise verb+resource+scope: a price estimate for a SPECIFIC Prague apartment given district and floor area. It distinguishes itself from siblings immediately, noting the data comes from realised sales in the land registry, not listings, and that it returns a mid estimate, range and CZK/m².

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?

It gives explicit when-to-use (user knows district + area, wants a specific apartment), when-not-to-use mappings to every relevant sibling (overeni_ceny_inzeratu for existing asking prices, ceny_bytu_lokalita for locality-level price, srovnani_ctvrti for comparisons, odhad_ceny_domu/odhad_ceny_pozemku for other property types), plus the rule for when area is missing.

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

All cenaodhad – ceny bytů v Praze z katastru 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