ikeytz Einsatzgebiet-Karten

Find By Gebiet

find_by_gebiet

Read-only

WHAT: Multi-match Gebiete by q, name, or slug (substring, umlauts ok). RETURNS all matching point cards. USE for fuzzy place names. DOES NOT require exact slug. NEXT: get_service_area for one, or get_grenze.

Input Schema

Name	Required	Description
`q`	No	Name or slug query (preferred)
`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
`q`	No	Resolved query
`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.
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`count`	No
`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.
`items`	No
`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.
`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.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedOutput schema / properties / items / items / properties / grenze_api

Added value: +{
+  "description": "https://maps.ikeytz.com/api/v1/embed/ort/{slug}/grenze (GeoJSON)",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / items / items / properties / punkt_api

Added value: +{
+  "description": "https://maps.ikeytz.com/api/v1/embed/ort/{slug}/punkt (GeoJSON Point)",
+  "format": "uri",
+  "type": "string"
+}

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 / q / description

Added value: +"Name or slug query (preferred)"

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"
+    },
+    "count": {
+      "type": "number"
+    },
+    "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"
+    },
+    "hint": {
+      "description": "Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.",
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "additionalProperties": true,
+        "description": "One Einsatzgebiet point card (not a polygon).",
+        "properties": {
+          "distance_km": {
+            "description": "Present on geo-ranked results: air distance from query point",
+            "type": "number"
+          },
+          "embed_map": {
+            "description": "https://maps.ikeytz.com/{slug}",
+            "format": "uri",
+            "type": "string"
+          },
+          "geo_api": {
+            "description": "https://maps.ikeytz.com/api/v1/embed/ort/{slug}",
+            "format": "uri",
+            "type": "string"
+          },
+          "google_maps": {
+            "description": "Paste-ready 'lat, lng'",
+            "type": "string"
+          },
+          "icbm": {
+            "description": "ICBM 'lat, lng' (same as google_maps)",
+            "type": "string"
+          },
+          "kind": {
+            "description": "stadtteil | ort",
+            "type": "string"
+          },
+          "lat": {
+            "description": "WGS84 latitude of THIS place",
+            "type": "number"
+          },
+          "lng": {
+            "description": "WGS84 longitude of THIS place",
+            "type": "number"
+          },
+          "maps_mcp": {
+            "const": "https://maps.ikeytz.com/mcp",
+            "description": "maps MCP endpoint",
+            "format": "uri",
+            "type": "string"
+          },
+          "name": {
+            "description": "German place name",
+            "type": "string"
+          },
+          "parent": {
+            "description": "Ludwigsburg or Landkreis Ludwigsburg",
+            "type": "string"
+          },
+          "plz": {
+            "description": "Postcode",
+            "type": "string"
+          },
+          "slug": {
+            "description": "maps slug",
+            "type": "string"
+          },
+          "url": {
+            "description": "Keyword/www page URL when present",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "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"
+    },
+    "q": {
+      "description": "Resolved query",
+      "type": "string"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "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"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4/5.0

Behavior4/5

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

readOnlyHint already covers the safety profile, and the description adds real value beyond it: substring matching, umlaut tolerance, and crucially 'RETURNS all matching point cards' (multi-match semantics, not a single result). It omits any note on result limits or ordering when many Gebiete match, which is the one behavioral gap left.

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/DOES NOT/NEXT structure is front-loaded and terse, with every clause carrying a distinct fact (matching mode, return shape, usage condition, follow-up). No filler sentences.

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 a full output schema covering return values and annotations covering safety, the description only needs to establish fuzzy-match semantics, which it does. Given the crowded find_by_* sibling set, a brief note on how it differs from find_by_plz or find_by_keyword would make it fully complete for selection.

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%, so q, name, and slug are already fully documented, including the slug-first lookup order. The description restates that lookups accept q/name/slug without adding format, precedence, or fallback detail the schema lacks; baseline 3 applies when the schema carries the parameter burden.

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?

States a specific verb+resource ('Multi-match Gebiete by q, name, or slug') with substring/umlaut qualifiers, so the agent knows this is fuzzy lookup rather than exact. It does not name the exact-match siblings (find_by_plz, find_by_serp) to contrast against, so the differentiation is by implication rather than by explicit callout.

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?

'USE for fuzzy place names' and 'DOES NOT require exact slug' give clear positive context plus one exclusion that separates it from exact-slug lookups. 'NEXT: get_service_area for one, or get_grenze' usefully routes follow-up calls, though it stops short of naming the sibling to prefer when the name is already known exactly.

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?