ikeytz Einsatzgebiet-Karten

Get Grenze

get_grenze

Read-only

WHAT: OSM Gebietspolygon for one Einsatzgebiet as GeoJSON FeatureCollection inside the MCP result. Same geometry as public GET https://maps.ikeytz.com/api/v1/embed/ort/{slug}/grenze (application/geo+json). Lookup slug|plz|name. RETURNS hasPolygon, polygon, point, osmRelationId/osmWayId, via, grenze_api, punkt_api. USE when the agent needs the boundary geometry. DOES NOT replace get_geo_api (URL pointers) or get_grenze_koordinaten (full embed blob). NEXT: get_grenze_koordinaten, get_lage, get_embed_map.

Input Schema

Name	Required	Description
`plz`	No	German postcode (PLZ). Several Gebiete can share one PLZ (e.g. 71638). For single lookup first match wins; use find_by_plz for all matches.
`name`	No	German place name substring (case-insensitive, umlauts ok), e.g. Grünbühl, Pattonville. Used when slug/plz omitted.
`slug`	No	URL slug of one of the 52 Einsatzgebiete, e.g. pattonville, bietigheim-bissingen, walheim, gruenbuehl. Matches https://maps.ikeytz.com/{slug}. Lookup order when combined with plz/name: slug first.

Output Schema

Name	Required	Description
`ok`	Yes	true = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.
`lat`	No
`lng`	No
`plz`	No
`via`	No	Fetch path hint
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`name`	No
`slug`	No
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`error`	No	Present when ok=false. Codes include: unknown_place, unknown_discovery, unknown_doc, q_required, plz_required, coords_required, outside_service_area, url_required, not_maps_host, bad_url, path_or_url_required, serp_not_found, slug_or_coords_required, path_required.
`point`	No	Point feature or null
`locale`	No	Locale actually used for URLs. maps is German-only: always de (MAPS-E8 — no /en on maps). Requested non-de is ignored; payload locale=de.
`geo_api`	No
`polygon`	No	GeoJSON FeatureCollection (may be empty)
`related`	No	Always includes https://maps.ikeytz.com/llms.txt.
`summary`	No	Primary text for the model. For discovery tools this is the file window. For list tools a compact one-liner. Quote with attribution.
`osmWayId`	No	OSM way id if any
`hasPolygon`	No	true if polygon.features length > 0
`attribution`	Yes	Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'
`canonicalUrl`	No	Best URL to show the user: https://maps.ikeytz.com… page, public embed JSON, tel:+49…, mailto:…, https://wa.me/…, or a www pointer. Prefer this over constructing URLs.
`osmRelationId`	No	OSM relation id if any

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 3, 2026

addedInput schema / properties / name / description

Added value: +"German place name substring (case-insensitive, umlauts ok), e.g. Grünbühl, Pattonville. Used when slug/plz omitted."

addedInput schema / properties / plz / description

Added value: +"German postcode (PLZ). Several Gebiete can share one PLZ (e.g. 71638). For single lookup first match wins; use find_by_plz for all matches."

addedInput schema / properties / slug / description

Added value: +"URL slug of one of the 52 Einsatzgebiete, e.g. pattonville, bietigheim-bissingen, walheim, gruenbuehl. Matches https://maps.ikeytz.com/{slug}. Lookup order when combined with plz/name: slug first."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Always the same envelope. tools/call returns content[0].text = summary (or JSON) AND structuredContent = this object. On success ok=true with summary + canonicalUrl + extra fields. On failure ok=false with error (snake_case code) and hint (recovery URL). Never writes, never submits forms, never books. Attribution must be kept when quoting. Policy: ai-input yes with attribution; ai-train=no. Host is maps.ikeytz.com (geo/Einsatzgebiet). Prices/FAQ/legal HTML live on www — maps only points.",
+  "properties": {
+    "attribution": {
+      "description": "Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'",
+      "type": "string"
+    },
+    "canonicalUrl": {
+      "description": "Best URL to show the user: https://maps.ikeytz.com… page, public embed JSON, tel:+49…, mailto:…, https://wa.me/…, or a www pointer. Prefer this over constructing URLs.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Present when ok=false. Codes include: unknown_place, unknown_discovery, unknown_doc, q_required, plz_required, coords_required, outside_service_area, url_required, not_maps_host, bad_url, path_or_url_required, serp_not_found, slug_or_coords_required, path_required.",
+      "type": "string"
+    },
+    "geo_api": {
+      "format": "uri",
+      "type": "string"
+    },
+    "hasPolygon": {
+      "description": "true if polygon.features length > 0",
+      "type": "boolean"
+    },
+    "hint": {
+      "description": "Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.",
+      "type": "string"
+    },
+    "lat": {
+      "type": "number"
+    },
+    "lng": {
+      "type": "number"
+    },
+    "locale": {
+      "description": "Locale actually used for URLs. maps is German-only: always de (MAPS-E8 — no /en on maps). Requested non-de is ignored; payload locale=de.",
+      "enum": [
+        "de"
+      ],
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "true = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.",
+      "type": "boolean"
+    },
+    "osmRelationId": {
+      "description": "OSM relation id if any",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "osmWayId": {
+      "description": "OSM way id if any",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "plz": {
+      "type": "string"
+    },
+    "point": {
+      "description": "Point feature or null",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "polygon": {
+      "description": "GeoJSON FeatureCollection (may be empty)",
+      "type": "object"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "type": "string"
+    },
+    "summary": {
+      "description": "Primary text for the model. For discovery tools this is the file window. For list tools a compact one-liner. Quote with attribution.",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Echo of the tool name that produced this object (e.g. get_service_area).",
+      "type": "string"
+    },
+    "via": {
+      "description": "Fetch path hint",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

AddedSep 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the behavioral burden. It adds that the geometry is returned inline inside the MCP result and enumerates the response fields (hasPolygon, polygon, point, osmRelationId/osmWayId, via, grenze_api, punkt_api), which tells the agent how this differs from pointer-returning siblings. It omits auth/permission needs or rate limits, keeping 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?

Labeled WHAT/RETURNS/USE/NEXT structure is front-loaded and scannable, with each sentence carrying distinct information (purpose, output fields, usage, alternatives, follow-ups). No filler sentences.

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?

An output schema exists, so return values need not be explained in prose, and the description still summarizes the shape. Combined with the explicit alternative tools and next steps, an agent has everything needed to select and 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 description coverage is 100%, and the schema already documents plz, name and slug including lookup precedence and examples. The description only restates 'Lookup slug|plz|name', adding no syntax or format detail beyond the schema, 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?

States a specific verb+resource: retrieves the OSM Gebietspolygon for one Einsatzgebiet as a GeoJSON FeatureCollection. It also explicitly names the sibling it is not (get_geo_api returns URL pointers, get_grenze_koordinaten returns the full embed blob), so an agent can distinguish it without opening other schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

'USE when the agent needs the boundary geometry' gives the triggering condition, and 'DOES NOT replace get_geo_api ... or get_grenze_koordinaten' supplies explicit exclusions with the reason for each. The NEXT line even suggests follow-on tools, leaving nothing to inference.

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

All ikeytz Einsatzgebiet-Karten tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?