Skip to main content
Glama

kataster_vlastnici

Retrieve the owners, ownership shares, LV number, and buildings for a single Slovak land registry parcel. Use it to identify who owns a specific parcel and their recorded shares.

Instructions

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.

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": {
      "ku": "<ku>",
      "cislo": "<cislo>"
    },
    "name": "kataster_vlastnici"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuYesCadastral unit (k.ú.): name or 6-digit code.
cisloYesParcel number, e.g. '503', 'E 503'. Exactly one parcel.
obnovitNoIgnore the 7-day cache and ask the portal again (counts towards the daily limit).
registerNoRegister C or E; 'auto' fails if the number exists in both.auto
potvrdeneNoOnly when a soft daily limit is configured: true after the user explicitly approved continuing.
detail_staviebNoAlso open the detail of each building on the parcel (LV of the building, kind, parcels under it, owners); each building is one more query towards the daily limit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior3/5

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

With no annotations, the description does substantial work: it discloses the unofficial ESKN source, human-pace querying with a daily parcel limit, a 7-day cache, per-building query cost for detail_stavieb, the returned fields, and personal-data restrictions. It stops short of stating whether failures are retryable or how a partial result (e.g., buildings without owners) is signalled, which matters for a scraping-backed tool.

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 identity of the tool, then source/limits, then returns, then the privacy rule and error path — a sensible order with no filler sentences. The return-value enumeration is long but justified because there is no output 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?

For a 6-parameter, no-output-schema tool backed by a rate-limited unofficial scraper, the description covers return shape, rate limits, caching, cost of the optional flag, privacy constraints, and error recovery. Little that an agent needs in order to call it correctly 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%, so the baseline is 3; the description earns an extra point by explaining what detail_stavieb actually produces (per-building LV, kind, C parcels, owners with shares, and that unit owners in a block of flats are not returned) and by noting it costs one query per building. That adds meaning beyond the schema's one-line parameter text.

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 sentence names a specific verb+resource ('Owners and shares ... of ONE parcel') plus the accompanying LV number, and the capitalization of ONE sets the scope unambiguously. The closing line explicitly routes a person-oriented lookup to kataster_osoba_navod, so an agent can separate this from sibling tools without opening schemas.

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 states the positive condition (the specific parcel the user asked about) and an explicit prohibition ('never walk parcels to find a person'), then names the alternative tool for the excluded case. It also tells the agent what to do on CAPTCHA, a block, or the daily limit — the error carries a navod guide for browser fallback.

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