Skip to main content
Glama

kataster_osoba_prehlad

Generate an overview of a person's land parcels and ownership shares from imported ownership sheets, including buildings, co-owner counts, and totals by cadastral unit.

Instructions

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í.

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_osoba_prehlad"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuNoOnly this cadastral unit (name or code).
icoNoLegal person: IČO (takes precedence over the name).
menoNoFirst name (natural person).
nazovNoLegal person: name.
priezviskoNoSurname (natural person).
datum_narodeniaNoDate of birth DD.MM.YYYY; without it namesakes are listed separately.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that no network request is made, that imports are retained only 7 days and expire, that co-owners are returned as a count only, that namesakes without a birth date are listed separately, and that bsm share belongs to both spouses. These are exactly the behavioral traits an agent needs before calling it.

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-loads purpose and the no-network/no-install caveat, then enumerates the per-LV return contents compactly. Dense domain jargon and semicolon-chained clauses make it harder to scan, but almost every clause carries information.

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 complex, six-optional-parameter query tool with no output schema, it describes the returned structure (per-LV parcels, buildings, share, share-area, co-owner count, totals) and the cache lifecycle, which is most of what an agent needs. It stops short of explaining empty-result behavior when no matching person exists, so it is thorough rather than complete.

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 each of the six parameters is already documented in the schema, setting the baseline at 3. The description reinforces the disambiguation rule for datum_narodenia and the natural-person vs legal-person split, but adds little parameter meaning beyond what the schema states.

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 ('Overview of a person's parcels'), names the data source (LVs imported with kataster_lv_import), and explicitly disclaims two confusable artifacts ('Not an LV extract and not the office's súpis nehnuteľností'). An agent can distinguish it from kataster_lv_import and kataster_lv 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear prerequisite (data must come from a prior kataster_lv_import) and an explicit remediation path: 'when LVs are missing or expired, call kataster_lv_import again on the same folder.' It does not contrast itself against other read tools such as kataster_vlastnici or kataster_parcela, so the routing guidance is strong but not exhaustive.

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