Skip to main content
Glama

cenaodhad – ceny bytů, domů a pozemků v Praze

Ověření ceny inzerátu / Asking price check

overeni_ceny_inzeratu
Read-onlyIdempotent

CZ: Použij, když uživatel (typicky kupující) má NABÍDKOVOU CENU bytu z inzerátu a chce vědět, jak si stojí proti skutečným prodejům. Porovná zadanou cenu s rozpětím realizovaných prodejů podobně velkých bytů ve stejné pražské čtvrti z katastru nemovitostí. Vrátí rozpětí, střed, rozdíl v % (formát „−6,2 %“), Kč/m² a pozici v pěti pásmech. Neutrální srovnání, ne verdikt. | Nepoužívej bez konkrétní ceny z inzerátu (→ odhad_ceny_bytu) ani pro domy a pozemky (→ odhad_ceny_domu, odhad_ceny_pozemku). Inzeráty nenačítá a odkazy neotevírá: čtvrť, plochu a cenu musí zadat uživatel nebo je vyčti z textu, který vložil. | EN: Use when the user (typically a buyer) has an ASKING PRICE for an apartment from a listing and wants to know how it compares with actual sales. Compares the given price with the range of realised sales of similar-sized apartments in the same Prague district from the Czech land registry. Returns range, middle, difference in % (format "−6,2 %"), CZK/m² and a five-band position. Neutral comparison, not a verdict. | Do not use without a specific listing price (→ odhad_ceny_bytu) or for houses and land (→ odhad_ceny_domu, odhad_ceny_pozemku). It does not fetch listings or open links: district, area and price must come from the user or from text they pasted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ctvrt": "<ctvrt>",
      "plocha_m2": "<plocha_m2>",
      "nabidkova_cena_kc": "<nabidkova_cena_kc>"
    },
    "name": "overeni_ceny_inzeratu"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctvrtYesNázev pražské čtvrtě (katastrální území) z inzerátu, ne obvod „Praha N“ ani ulice; diakritika nevadí. Např. "Vinohrady" / Prague district (cadastral area) from the listing, not a "Praha N" borough or a street; diacritics optional. E.g. "Vinohrady"
jazykNoJazyk odpovědi / Response languagecs
plocha_m2YesPlocha bytu v m² podle inzerátu jako číslo, 15–250, např. 60 / Apartment area in m² from the listing as a number, 15–250, e.g. 60
nabidkova_cena_kcYesNabídková cena z inzerátu v celých Kč jako číslo bez mezer a měny, 500 000–200 000 000, např. 8900000 pro 8,9 mil. Kč / Asking price in whole CZK as a plain number, 500,000–200,000,000, e.g. 8900000 for CZK 8.9 million

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / ctvrt / description
      Previous value: -"Název pražské čtvrtě (katastrální území), např. \"Vinohrady\" / Prague cadastral district"New value: +"Název pražské čtvrtě (katastrální území) z inzerátu, ne obvod „Praha N“ ani ulice; diakritika nevadí. Např. \"Vinohrady\" / Prague district (cadastral area) from the listing, not a \"Praha N\" borough or a street; diacritics optional. E.g. \"Vinohrady\""
    • changedInput schema / properties / nabidkova_cena_kc / description
      Previous value: -"Nabídková cena z inzerátu v Kč / Asking price in CZK"New value: +"Nabídková cena z inzerátu v celých Kč jako číslo bez mezer a měny, 500 000–200 000 000, např. 8900000 pro 8,9 mil. Kč / Asking price in whole CZK as a plain number, 500,000–200,000,000, e.g. 8900000 for CZK 8.9 million"
    • changedInput schema / properties / plocha_m2 / description
      Previous value: -"Plocha bytu v m² podle inzerátu, 15–250 / Apartment area in m², 15–250"New value: +"Plocha bytu v m² podle inzerátu jako číslo, 15–250, např. 60 / Apartment area in m² from the listing as a number, 15–250, e.g. 60"
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real context beyond that: the return content (range, middle, % difference, CZK/m², five-band position), that the result is a neutral comparison rather than a verdict, and that it does not fetch listings or follow links. Auth and rate-limit behavior remain unstated.

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 the use case, then method, return values, and exclusions in a clear order. The main cost is the full CZ/EN duplication, which roughly doubles length, though the structure itself is clean and every section is 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?

Although there is no output schema, the description enumerates the return values (range, middle, % difference, CZK/m², five-band position) and the neutral framing, so nothing an agent needs to call or interpret the tool 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 coverage is 100% with ranges, examples and a CZK format hint, so the baseline is 3. The description adds sourcing guidance: čtvrť, plocha and cena must come from the user or be extracted from pasted text, which resolves a practical ambiguity about parameter origin not covered by the schema.

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?

States a precise verb+resource: it verifies a listing ASKING PRICE against the range of realised sales of similar-sized flats in the same Prague district from the land registry. It explicitly distinguishes itself from siblings (odhad_ceny_bytu for cases without a price, odhad_ceny_domu/odhad_ceny_pozemku for houses/land), so an agent can route correctly 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?

Gives explicit when-to-use (buyer has an asking price and wants to compare it against actual sales) and when-not-to-use, naming the alternatives for each exclusion case. The extra constraint that data must come from the user or pasted text, and that it does not fetch listings or open links, removes a common misuse path.

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.

Resources