Skip to main content
Glama

kataster_skupina

Analyse a group of parcels from official geometry: compute each parcel's area and total, detect shared boundaries and contiguity, and find the nearest reference parcel with distance.

Instructions

Analyse a group of parcels from official geometry (no owners).

Returns each parcel's area, the total, which group parcels share a boundary with each other (length in m), whether the group is one contiguous block, the nearest reference parcel with distance in m, and optionally all neighbouring parcels.

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": {
      "parcely": "<parcely>"
    },
    "name": "kataster_skupina"
  }
}

Input Schema

NameRequiredDescriptionDefault
parcelyYesParcels of the group (max 50).
susediaNoAlso list neighbouring parcels from the WFS (same register) with shared boundary length.
referencneNoReference parcels (e.g. own land); for each group parcel the nearest one and the distance.

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 burden and does most of it well: it enumerates the computed outputs (per-parcel area, total, pairwise shared boundary lengths, contiguity flag, nearest reference parcel distance, optional neighbours), which is real behavioral disclosure. It never states explicitly that this is a read-only operation or what happens on lookup failure, so it stops short of full coverage.

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?

Two sentences, front-loaded with purpose and scope before the return-value enumeration; the list is informative rather than padding. Slightly dense but no sentence is wasted.

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?

No output schema and no annotations, so the description must supply the return picture — and it does so thoroughly. Remaining gaps (read-only status, error behavior, the 50-parcel limit) are minor since the limit is already in the schema.

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% and the schema already explains 'susedia' and 'referencne' in detail. The description adds output-level meaning (neighbours with shared boundary length, nearest reference parcel and distance) but no new constraints or syntax beyond what the schema states, so the baseline 3 applies.

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 description opens with a specific verb and resource ('Analyse a group of parcels from official geometry') and immediately scopes it with '(no owners)', which separates it from ownership-oriented siblings such as kataster_vlastnici or kataster_parcela. An agent can tell what this does 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 Guidelines3/5

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

Usage is only implied: the '(no owners)' qualifier hints that ownership lookups belong to other tools, and the group framing hints at multi-parcel vs single-parcel tools. There is no explicit when-to-use, when-not-to-use, or named alternative.

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