Skip to main content
Glama

kataster_lv

Generates the ESKN portal URL for a Slovak land registry LV extract and explains preview vs. official extract, with no network request or reCAPTCHA bypass.

Instructions

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.

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>",
      "lv": "<lv>"
    },
    "name": "kataster_lv"
  }
}

Input Schema

NameRequiredDescriptionDefault
kuYesCadastral unit (k.ú.): name or 6-digit code.
lvYesLV number (číslo listu vlastníctva), e.g. from kataster_vlastnici.
formatNohtml can be imported with kataster_lv_import; pdf is for printing.html
parcelyNoOptional parcels for a partial extract (čiastočný výpis), e.g. ['E 503']. Register prefix required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4/5.0
Behavior5/5

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

With no annotations present, the description carries the full burden and does it well: it states plainly that no network request is made, that the ESKN reCAPTCHA must be solved by the user and will never be bypassed, and that this is the only public source for encumbrances and tenant data. These are exactly the constraints (blocked automation, user-in-the-loop requirement) an agent must know before calling.

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?

It front-loads the deliverable in the first line, then adds constraint and workflow context in short sentences that each carry information. Slightly long for a four-parameter tool, but nothing is filler.

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 tool that returns a URL plus a guide and has no output schema, the description covers what comes back, why it cannot fetch directly, and how to sequence the user interaction. Nothing 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so ku, lv, format, and parcely are already fully documented, including the note that html can be imported with kataster_lv_import and that parcely requires a register prefix. The description body adds no parameter meaning beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the concrete deliverable (a URL of the LV extract on ESKN plus a navod guide) rather than a vague action, so an agent knows this tool hands back a link and instructions instead of data. It does not explicitly distinguish itself from siblings such as kataster_lv_import or kataster_vlastnici in the description body, which keeps it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: the tool is for situations needing encumbrances (ťarchy, časť C), administrators, and tenants, and the agent is told to walk the user through step by step. There is no explicit when-not or named alternative, so the routing guidance depends on inference.

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