Skip to main content
Glama

slovenia-cadastral-simple

Query Slovenian cadastral data - resolve parcels, addresses, buildings, and find properties by location.

COMMANDS & EXAMPLES:

  1. PARCEL - Find all addresses on a specific parcel Example: --command parcel --parcel-num 3086 --ko-id 1725 Returns: Parcel details with all addresses located on it

  2. ADDRESS - Find which parcel contains a street address Example: --command address --street "Trg republike" --house-number 1 --city Ljubljana Returns: Parcel information for that address

  3. BUILDING - Get building details and its parcel Example: --command building --building-num 1234 --ko-id 1728 Returns: Building info and associated parcel

  4. NEAR-COORDS - Find parcels near GPS coordinates Example: --command near-coords --lat 46.058 --lon 14.501 --radius 100 --limit 20 Returns: List of parcels within radius, sorted by distance

  5. NEAR-LOCATION - Find parcels near a named place (built-in geocoder) Example: --command near-location --location-name "Tivoli Park Ljubljana" --radius 200 --limit 10 Returns: Geocoded location + parcels within radius

All outputs are JSON format. Use --help for more details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude in WGS84 (Slovenia: 45.4-46.9). Example: 46.058
lonNoLongitude in WGS84 (Slovenia: 13.3-16.6). Example: 14.501
cityNoCity or settlement name. Example: Ljubljana
ko_idNoCadastral municipality ID. Example: 1725 (Ljubljana)
limitNoMaximum number of results. Example: 10
radiusNoSearch radius in meters. Example: 200
streetNoStreet name. Example: Trg republike
commandYesCommand: parcel, address, building, near-coords, or near-location
parcel_numNoParcel number (for parcel command). Example: 3086
building_numNoBuilding number. Example: 1234
house_numberNoHouse number. Example: 1
location_nameNoPlace name to geocode. Example: Tivoli Park Ljubljana

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only, any authentication requirements, rate limits, data freshness, or side effects. It only describes functionality without behavioral constraints.

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?

The description is well-structured with clear command headings and examples, but it is verbose. It could be more concise by reducing example repetitions. However, the layout aids readability and quick understanding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks an output schema and does not detail the structure of the JSON response beyond stating 'All outputs are JSON format.' It also omits error handling or edge cases. For a tool with 12 parameters and no output schema, more completeness is needed.

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?

With 100% schema description coverage, the schema already documents all parameters. The description's examples (e.g., --parcel-num 3086 --ko-id 1725) add marginal context by showing usage, but do not significantly enhance parameter semantics beyond the schema.

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 clearly states the tool's purpose: 'Query Slovenian cadastral data - resolve parcels, addresses, buildings, and find properties by location.' It then lists five specific commands with examples, making the purpose unambiguous and differentiating it from siblings like slovenia-cadastral-deep.

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?

The description provides explicit commands and examples for each use case, guiding when to use each sub-command. However, it does not differentiate this tool from its sibling slovenia-cadastral-deep, which could provide more detailed queries. The name 'simple' implies a simpler interface, but this is not explicitly stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (geocoding vs routing vs POI search). However, the multiple Slovenian cadastral tools (simple, deep, wfs-expert) overlap in functionality, potentially confusing an agent on which to use for a given task.

Naming Consistency3/5

Tools within subgroups like 'geo-*' follow a consistent verb_noun pattern, and 'slovenia-*' tools use a noun_adjective pattern. However, across the whole set there is no unified naming convention, mixing prefixes like 'eu-', 'events-', 'hikes-', and 'hostel-'.

Tool Count4/5

With 16 tools, the server is slightly above the ideal range (3-15) but still well-scoped. Each tool addresses a distinct geographic need, although the breadth across many domains (transit, cadastre, weather, hostels) feels a bit broad.

Completeness4/5

The tool set covers core geographic operations (geocoding, routing, POI, isochrones, reverse geocoding) plus specialized Slovenian data and travel amenities. Minor gaps exist, such as lack of general worldwide POI beyond OSM or event discovery beyond Luma, but overall it is comprehensive for its domain.

Resources