Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
KATASTER_DATA_DIRNoCesta k dátovému adresáru (cache a uložené LV). Má prednosť pred predvolenými umiestneniami na Linuxe, macOS a Windows a platí pre MCP server aj príkazový riadok. Stav limitov zostáva na pevnom mieste.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Slovak land registry (kataster nehnuteľností SR). Look up a cadastral unit (k.ú., katastrálne územie) with kataster_ku, then a parcel (parcela, register C or E) with kataster_parcela. Every answer carries its sources (zdroje) with time and whether it came from the local cache. Data are informative, not an official extract (výpis z LV). Where the server cannot go itself (CAPTCHA, official search by person, eID) an answer or error carries 'navod': steps for the user; walk the user through them one at a time.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
kataster_vlastniciA

Owners and shares (vlastníci a podiely) of ONE parcel, with the LV number (list vlastníctva).

Source: the unofficial ESKN portal parcel detail, queried at human pace with a daily limit on parcels. Returns LV number, land type (druh pozemku), location in/outside the built-up area, legal relation, owners (name, birth date, address, share), buildings on the parcel (stavby: house number only; a building may be on another LV than the land) and the data date (stav_k). With detail_stavieb=true also stavby_detail: per building its LV, kind, description, C parcels under it and owners with shares (a block of flats: unit owners are not returned); stavby_dotazy = queries spent. Personal data: use only for the parcel the user asked about; never walk parcels to find a person (for a person's parcels use kataster_osoba_navod). On CAPTCHA, a block or the daily limit the error carries a guide (navod) for doing the same in the browser.

kataster_vrstvyA

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.

kataster_skupinaA

Analyse a group of parcels from official geometry (no owners).

Returns each parcel's area, the total, which group parcels share a boundary with each other (length in m), whether the group is one contiguous block, the nearest reference parcel with distance in m, and optionally all neighbouring parcels.

kataster_mapaA

Draw parcels on a map and save files. Returns the file paths.

PNG is rendered on the server (background from official WMS, outlines, labels, scale bar, attribution). HTML is an interactive Leaflet map with the same background embedded and, when the parcels lie apart, a sharp crop (vyrezy) per cluster of near parcels above it, so zooming in stays readable; each crop costs one request per background source (podklad_dotazy). GeoJSON/KML contain only geometry and public attributes (no owners).

kataster_lvA

URL of the LV extract (výpis z LV) on the ESKN portal and a guide (navod) for the user.

Makes no network request. The portal shows a reCAPTCHA ('Nie som robot') that only the user may solve; this tool never bypasses it. The extract is the only public source of encumbrances (ťarchy, časť C), administrators and tenants. The guide explains LV preview vs. extract vs. official extract (eID, paid); walk the user through it one step at a time.

kataster_lv_importA

Read LV extracts (výpis z LV, HTML or PDF) and LV previews (Náhľad LV, HTML) saved from the browser.

One file: returns the parsed LV: header (district, municipality, k.ú., date of data), part A (parcels with area, land type, location; codes translated by the legend; buildings in stavby with súpisné číslo, the parcel under the building, kind and the LV of the land), part B (owners with shares, acquisition titles, notes; administrators and tenants) and part C (encumbrances, ťarchy). A block of flats lists its units in jednotky (flat or non-residential premises, entrance, floor, share of the common parts) and each owner of a unit carries jednotka. zdroj_typ tells the input: vypis_lv_html, vypis_lv_pdf or nahlad_lv (the preview has no administrators/tenants section). A folder or several paths: a summary per LV (the same LV twice is merged: newer data, extract before preview), unreadable files are listed in varovania. Makes no network request. Results are kept in the local personal-data cache for 7 days (owner-only permissions on POSIX); kataster_osoba_prehlad reads them.

kataster_osoba_navodA

Guide (navod) for finding the parcels of a person in ONE k.ú. in the official ESKN search, by the user.

The server never searches by person and makes no network request here: the user searches in the browser (the portal's invisible CAPTCHA lets a person through), opens the LV previews, saves them into one folder, then kataster_lv_import reads the folder and kataster_osoba_prehlad builds the overview. The search is per k.ú., not per municipality: a town can have several k.ú. (ine_ku_obce) and a property "in village X" can lie in a neighbouring village's k.ú.; repeat the guide for every k.ú. that matters. Walk the user through the steps ONE AT A TIME (wait until a step is done), do not paste the whole list.

kataster_osoba_prehladA

Overview of a person's parcels from LVs imported with kataster_lv_import (no network request).

Per LV: k.ú., parcels (register, number, area, land type), buildings (súpisné číslo, the parcel under it, kind; lv_pozemku = the LV of the land when it is elsewhere), the person's share, the area by share, how many other co-owners (count only); bsm = joint property of spouses (the share belongs to both). Totals per person. Without a date of birth, people with the same name are listed separately. Imports are kept 7 days; when LVs are missing or expired, call kataster_lv_import again on the same folder. Not an LV extract and not the office's súpis nehnuteľností.

kataster_kuA

Find a cadastral unit (katastrálne územie, k.ú.) by name or code.

Returns [{kod, nazov, obec, obec_kod, okres, lat, lon}]; lat/lon is a point inside the unit. Municipality (obec) and district (okres) tell apart units with the same name (128 names repeat). Works offline from a bundled list.

kataster_parcelaA

Parcel (parcela) geometry from the official INSPIRE WFS of ÚGKK SR.

Give either ku + cislo, or lat + lon (returns every C and E parcel at that point). Returns register, number, area in m² (výmera), reference point (referencny_bod, a point guaranteed inside the parcel), bbox and optionally the polygon. No owners here.

kataster_statusA

Server status: access policy, today's owners quota, cache contents and parser versions.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 11 tools

Disambiguation4/5

Most tools have distinct resource+action purposes (geometry, owners, layers, map, group analysis). The four-tool LV/person family (kataster_lv, kataster_lv_import, kataster_osoba_navod, kataster_osoba_prehlad) and kataster_vlastnici vs kataster_lv could be momentarily confused, but descriptions tightly scope each (URL+guide vs file parsing vs step-by-step guidance vs aggregated overview vs per-parcel owners).

Naming Consistency5/5

Every tool follows the same kataster_<noun> snake_case pattern, with nested variants (kataster_lv_import, kataster_osoba_navod) staying readable and predictable. No camelCase or verb-style mixing; the noun-based convention is used uniformly.

Tool Count5/5

11 tools is well within the ideal 3-15 range for a rich cadastral domain. Each tool earns its place: geometry, owners, thematic layers, maps, LV handling, person workflow, unit lookup, group analysis and status are all non-redundant.

Completeness4/5

Core CRUD-like lifecycle for cadastral queries is well covered: k.ú. lookup, parcel geometry, owners, thematic layers, LV access/import, person overview, group analysis and map export. Gaps are minor and partly deliberate (no owner-based search by design, no address-to-parcel lookup, no plain 'list parcels in k.ú.'), which agents can work around.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues