Skip to main content
Glama

kataster_vrstvy

Retrieves thematic land-registry layers for a parcel or point—soil quality, land value, farming, flood risk, protection, slope, forest and utilities—to support land and site assessment.

Instructions

Thematic layers for a parcel (whole polygon, with area shares) or a point.

  • bpej: soil-ecological units (BPEJ) with quality group (skupina kvality), points, protected soil, levies for taking farmland (odvod za záber) — VÚPOP

  • hodnota: official land value €/m² for land consolidation (vyhl. 38/2005), not a market price — VÚPOP

  • lpis: farm blocks (diel pôdneho bloku, LPIS) and land use — VÚPOP

  • uzivatel: who farms the land per subsidy applications (name, IČO, year) — NLC

  • zaplavy: flood hazard extent Q10/Q100/Q1000 and depth class — SVP

  • ochrana: Natura 2000 (CHVÚ, ÚEV), protected areas and degree of protection — ŠOP SR

  • vyska: elevation at the reference point (DMR 5.0) — ÚGKK

  • zastavane_uzemie: parcel inside or outside the built-up area of the municipality — cadastral map WMS of ÚGKK (register C, official) or ESKN identify (register E, unofficial)

  • tarchy: whether a drawn encumbrance (ťarcha) line crosses the parcel, with internal ids; an unofficial estimate from the rendered cadastral map, parcels only (not points); content only in the LV (kataster_lv)

  • pozemkove_upravy: land consolidation projects (in progress / finished, complex / simple) in the parcel's cadastral unit, with years and project area — MPRV SR open data; parcels only; says nothing about whether the parcel lies inside the project boundary

  • les: forest management units (JPRL: compartment, stand group, forest category hospodársky / ochranný / osobitného určenia, forest unit, management plan validity) and forest types, with area shares — NLC; no forest owner or manager

  • siete: access and line objects — nearest ZBGIS road (type, surface, distance; adjacent if <= 3 m) and roads, railways and power lines (voltage) crossing the parcel or within 50 m, with distance and length on the parcel — ZBGIS of GKÚ; parcels only; protection zones are not computed (warning only)

  • sklon: terrain slope of the parcel (mean, max, 95th percentile in % and degrees), prevailing exposure (S, SV, V, JV, J, JZ, Z, SZ = N, NE, E, SE, S, SW, W, NW, or rovina = flat), min/max height and difference — DMR 5.0 1 m grid of ÚGKK (INSPIRE WCS); parcels only A failing layer does not fail the others; it carries its own chyba.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kataster_vrstvy"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuNoCadastral unit (k.ú.): name or 6-digit code.
latNoLatitude WGS84, instead of a parcel.
lonNoLongitude WGS84, instead of a parcel.
cisloNoParcel number, e.g. '503', 'E 503'.
vrstvyNoLayers to return; default all.
registerNoRegister C or E; 'auto' fails if the number exists in both.auto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the whole burden and does well: it names the data source behind each layer (VÚPOP, NLC, SVP, ŠOP SR, ÚGKK, ZBGIS), flags accuracy limits (tarchy is an 'unofficial estimate', siete gives a 'warning only' for protection zones), and discloses that 'a failing layer does not fail the others; it carries its own chyba'. It does not describe the overall response shape, auth or rate behavior, but the per-layer failure semantics are the operationally important disclosure.

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 and input modes are front-loaded, followed by a scannable bullet per layer, each sentence carrying a source, a caveat or a scope restriction. The length is justified by 13 enum values, though a few bullets (les, siete) pack multiple disjoint facts and the important error-isolation note is buried at the end.

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?

For a six-parameter read tool with no output schema and no annotations, the description is complete enough: it explains what each layer returns, its provenance, its limitations and its failure mode. What it omits is the minimum required to identify a target (the ku/cislo vs lat/lon split) and any hint about response volume, but the schema covers the former.

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%, so the schema documents inputs, but the description goes beyond it by giving meaning to every value of the `vrstvy` enum, which the schema lists only as bare strings. It also explains the register C/E distinction (official vs unofficial) that underlies the `register` parameter, though it does not add anything about the 'auto' failure mode already in 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?

The first line states a specific verb and resource: 'Thematic layers for a parcel (whole polygon, with area shares) or a point,' and the 13 bullets enumerate exactly which thematic enrichments are available. This is far more specific than the bare name and lets an agent distinguish it from parcel-identity tools like kataster_parcela or kataster_lv.

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?

The definition gives real selection guidance inside the layer list: 'parcels only (not points)' for tarchy, pozemkove_upravy, siete and sklon, and a direct routing pointer that encumbrance content lives in kataster_lv. It does not state the sequencing against siblings such as kataster_parcela to first resolve a parcel, so it stops short of full when/when-not guidance.

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