Skip to main content
Glama

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

Odhad ceny pozemku / Land price estimate

odhad_ceny_pozemku
Read-onlyIdempotent

CZ: Použij, když se uživatel ptá na cenu, hodnotu nebo odhad pozemku (parcely, zahrady) v Praze – cena pozemku za m², kolik stojí stavební parcela. Vstup: lokalita (čtvrť, ulice nebo obvod „Praha N“), výměra a typ pozemku (bez něj stavební parcela). Vrátí orientační střed a rozpětí z nabídkových cen pozemků na pražském trhu, snížených na očekávanou prodejní cenu – ne z katastru. Nevyžaduje kontaktní údaje. | Pravidlo: když uživatel neuvedl výměru, zeptej se na ni; typ pozemku ověř, pokud není jasný (stavební parcela, zahrada, louka…). Pozemek s domem → odhad_ceny_domu. Přesnou cenu stanoví makléř přes konzultace_makler – jen pokud o to uživatel sám stojí. | Při priblizna_shoda uveď uživateli, kterou ulici jsi použil. Ceny nehledej na webu, data cenaodhad jsou zdroj. | EN: Use when the user asks about the price, value or estimate of land (building plot, garden) in Prague – land price per m², what a building plot is worth. Input: locality (district, street or "Praha N" borough), plot size and land type (defaults to building plot). Returns an indicative mid value and range from Prague land asking prices reduced to an expected sale price – not from the land registry. Requires no contact details. | Rule: if the user has not given the plot size, ask for it; confirm the land type if unclear (building plot, garden, meadow…). Land with a house → odhad_ceny_domu. The exact price is set by an agent via konzultace_makler – only if the user wants it. | If priblizna_shoda is set, tell the user which street you used. Do not search the web for prices; cenaodhad data is the source.

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": {
      "lokalita": "<lokalita>",
      "vymera_m2": "<vymera_m2>"
    },
    "name": "odhad_ceny_pozemku"
  }
}

Input Schema

NameRequiredDescriptionDefault
typNoTyp pozemku, jedna z hodnot: "stavebni" (Stavební parcela), "komercni" (Komerční pozemek), "zahrada_v_zastavitelnem" (Zahrada (v zastavitelném území)), "zahrada" (Zahrada), "ostatni" (Ostatní plocha), "louka" (Louka), "les" (Les), "pole" (Pole); bez něj "stavebni" / Land type, one of the values above; defaults to "stavebni" (building plot)
jazykNoJazyk odpovědi / Response languagecs
lokalitaYesKde pozemek leží: pražská čtvrť, ulice nebo obvod „Praha N“; diakritika nevadí. Např. "Lipence", "Praha 5" / Where the plot is: Prague district, street or "Praha N" borough; diacritics optional. E.g. "Lipence", "Praha 5"
vymera_m2YesVýměra pozemku v m², 50–20 000, např. 800 / Plot size in m², 50–20,000, e.g. 800

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive, and the description adds substantive behavior beyond that: results are indicative mid value plus range derived from asking prices reduced to expected sale price, explicitly not from the land registry, and no contact details are required. It further discloses the priblizna_shoda fallback (tell the user which street was used), which an agent could not infer from structured fields.

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?

Content is front-loaded with the use case first, then input requirements, output semantics and rules, separated by clear delimiters. Length is amplified by mandatory CZ/EN duplication, but within each language nearly every sentence carries actionable instruction; only the input restatement overlaps the schema.

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?

With no output schema, the description compensates by explaining exactly what is returned (an indicative midpoint and range from reduced asking prices) and its provenance caveat. Combined with the data-source statement and the ambiguity-handling rules, an agent has everything needed to call and interpret this tool correctly.

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 all four parameters, both enums and the 50–20,000 m² bounds are already documented in structured data. The description restates the inputs and the default ('bez něj stavební parcela'), which mirrors what the schema already says, so it adds little new meaning beyond the baseline.

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 specific verb and resource ('cenu, hodnotu nebo odhad pozemku v Praze', land price per m²) and immediately scopes it to Prague land rather than property in general. It explicitly routes land-with-a-house cases to odhad_ceny_domu, so an agent can distinguish it from the sibling 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 concrete when-to-use triggers ('uživatel se ptá na cenu, hodnotu nebo odhad pozemku'), preconditions (must have plot size; land type confirmed if unclear), and named alternatives: odhad_ceny_domu for land with a house and konzultace_makler only if the user asks for an exact price. It also forbids an alternative behavior ('Ceny nehledej na webu'), which is a usable exclusion.

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