Skip to main content
Glama

kataster_parcela

Retrieve Slovak land parcel geometry from official INSPIRE WFS by cadastral unit and parcel number or WGS84 coordinates; returns register, area, reference point, bbox and optional polygon.

Instructions

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.

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

Input Schema

NameRequiredDescriptionDefault
kuNoCadastral unit (k.ú.): name or 6-digit code.
latNoLatitude WGS84, instead of ku+cislo.
lonNoLongitude WGS84, instead of ku+cislo.
cisloNoParcel number, e.g. '503', '660/66', 'E 503'.
registerNoRegister: C (parcely registra C, current plots) or E (registra E, original ownership plots). 'auto' tries both.auto
geometriaNoInclude the GeoJSON polygon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does reasonably well: it discloses that point queries return multiple parcels, that referencny_bod is guaranteed inside the parcel, and that the polygon is optional. It omits error/empty-result behavior and any auth or rate-limit notes, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and source, then the input modes, then the return contents. Every sentence carries information; nothing is redundant.

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?

With no output schema, the description correctly enumerates the return fields (register, number, area in m², reference point, bbox, optional polygon). It leaves out what happens when no parcel matches and the exact serialization format, minor gaps for a lookup tool.

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 baseline is 3, but the description adds real meaning: it explains the two mutually exclusive input modes (ku+cislo vs lat+lon) and that geometria optionally includes the polygon. This clarifies how parameters interact rather than restating them.

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+resource ('Parcel geometry from the official INSPIRE WFS of ÚGKK SR') and explicitly scopes out owner data ('No owners here'), which separates it from siblings like kataster_vlastnici. An agent can identify the tool's output without opening the 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 clear input-mode guidance: 'Give either ku + cislo, or lat + lon', and notes the point mode returns every C and E parcel at that location. It does not name an alternative tool for owner lookups, but the 'No owners here' note implies the boundary.

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