Skip to main content
Glama

Public-law restrictions on a parcel (ÖREB)

get_land_restrictions
Read-only

Retrieve ÖREB land restrictions for a parcel by WGS84 coordinates or EGRID, including applicable and non-applicable themes, legal status, affected area, and the official PDF extract.

Instructions

ÖREB cadastre extract for the land parcel at a point (WGS84) or by EGRID: which restriction themes concern the parcel (land-use zoning, building lines, noise sensitivity, groundwater protection, contaminated sites, …), each restriction with legend text, legal status, affected area/percentage and links to the legal provisions; plus the themes that do NOT concern it. Includes the link to the official PDF extract (the only legally binding version). Use geocode first for an address. Example: {lat: 47.3769, lon: 8.5417}.

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": "get_land_restrictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNoWGS84 latitude inside the parcel
lonNoWGS84 longitude inside the parcel
langNoLanguage of the extract (cantons publish de/fr/it; others fall back)de
egridNoFederal parcel id (EGRID), e.g. 'CH399977799134'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description adds real value: it discloses that results include themes that do NOT concern the parcel, per-restriction legend text, legal status and area percentages, and the critical caveat that only the linked official PDF is legally binding. It does not cover failure modes (point outside Switzerland, point not inside a parcel), which is a minor gap for a geospatial lookup.

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 core content is front-loaded in the first clause ('ÖREB cadastre extract for the land parcel...'), followed by a usage rule and a concrete example. The first sentence is long and densely packed with comma-separated clauses, which costs a little readability but no sentence is filler.

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 must carry the return-value burden, and it does — listing restriction themes, per-theme attributes, negative themes, and the PDF link. Combined with 100% schema coverage and safety annotations, an agent has enough to invoke it correctly; only error/edge-case behavior is unaddressed.

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 the baseline is 3; the description goes beyond it by making the either/or relationship explicit (coordinate pair OR EGRID) even though the schema marks no parameter as required, and by supplying a concrete example object. It does not add format guidance beyond what the schema's pattern and ranges already provide.

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 names a specific resource (ÖREB cadastre extract for a land parcel) and enumerates the restriction themes returned (zoning, building lines, noise, groundwater, contaminated sites). It distinguishes itself from the sibling geocode by routing address lookups there, so an agent can tell what it 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 Guidelines4/5

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

It gives one explicit routing rule — 'Use geocode first for an address' — and clarifies the input alternatives (point in WGS84 or EGRID). It does not state when NOT to use it or name any other alternative for parcel-level legal data, so it falls short of full when/when-not coverage.

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

Deploy Server

Other Tools