Skip to main content
Glama

kataster_ku

Find a Slovak cadastral unit by name or 6-digit code, even without diacritics. Returns code, municipality, district and a point inside the unit, working offline from a bundled list.

Instructions

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.

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": {
      "query": "<query>"
    },
    "name": "kataster_ku"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesName of the cadastral unit (k.ú.), diacritics optional, or its 6-digit code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior4/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 reasonably well: it discloses the exact return fields, clarifies that lat/lon is a point inside the unit (not a centroid of anything larger), and states that it works offline from a bundled list, which tells the agent no network or auth is involved. It is implicitly a read-only lookup but never says so outright, and it does not describe result ordering or limits.

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?

Three short lines, each doing distinct work: purpose first, then return shape, then disambiguation, then the offline note. Nothing is redundant, and the most decision-relevant information is front-loaded.

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?

There is no output schema, so the description's return-field list is exactly the missing piece an agent needs. For a single-parameter lookup tool with no annotations, purpose, return shape, ambiguity handling, and offline behavior together cover everything required to call it correctly.

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 the single query parameter is already fully documented as a name with optional diacritics or a 6-digit code. The description restates that same information rather than adding syntax or format detail. The one genuinely useful addition, the note that 128 names repeat and obec/okres disambiguate them, concerns interpreting results rather than the parameter itself.

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 opens with a specific verb and resource: 'Find a cadastral unit (katastrálne územie, k.ú.) by name or code.' That is unambiguous about what the tool retrieves and what it searches on. It does not explicitly contrast itself with siblings such as kataster_parcela or kataster_lv, so it stops short of full sibling differentiation.

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: an agent infers it should call this when it needs to resolve a cadastral unit name or code. There is no explicit when-to-use, when-not-to-use, or named alternative, and no stated prerequisites. The line about the bundled offline list gives context but is not routing guidance.

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