ikeytz Einsatzgebiet-Karten

Get Service Area

get_service_area

Read-only

WHAT: One Einsatzgebiet by slug → plz (first match) → name substring. RETURNS point card + maps_nav (hub/buero/mcp-hub) + neighbors (5 nearest by airline, MAPS-IL2) + optional Lage texts (h1, kicker, blurb, lage, geschichte) unless compact=true. fields= filters keys. USE when the user names a town/district in Landkreis Ludwigsburg. DOES NOT geocode free addresses outside the 52; unknown → ok=false unknown_place. NEXT: get_lage, get_geschichte, get_grenze, get_embed_map, distance_to_office.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`fields`	No	Optional field filter: comma-separated names or array. Keeps envelope keys (ok, tool, summary, canonicalUrl, attribution, locale, related, count, total, offset, limit, compact) plus listed fields. Example: slug,name,plz,lat,lng.
`locale`	No	maps is German-only (de). Omit or pass de. Other values are ignored; URLs stay https://maps.ikeytz.com/… with no locale prefix. Not a www multi-locale switch — use @ikeytz/mcp list_locales on www for en\|fr\|ru\|fa\|ar\|tr.	de
`compact`	No	If true, omit h1/kicker/blurb/lage/geschichte — coords + URLs + neighbors still present.

Output Schema

TableJSON Schema

Name	Required	Description
`h1`	No	Visitenkarte H1 when not compact
`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	Place latitude
`lng`	No	Place longitude
`plz`	No	Postcode
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`icbm`	No	ICBM string
`kind`	No	stadtteil \| ort
`lage`	No	Lage text when not compact
`name`	No	German name
`slug`	No	Resolved slug
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`blurb`	No	Short blurb when not compact
`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.
`kicker`	No	Kicker when not compact
`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.
`parent`	No	Parent label
`walkIn`	No	Always false
`compact`	No	Whether compact mode was applied
`geo_api`	No
`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.
`maps_nav`	No	MAPS-IL1 mini-chrome URLs
`embed_map`	No
`neighbors`	No	Up to 5 nearest Gebiete (slug/name/embed_map)
`geschichte`	No	Geschichte text when not compact
`office_lat`	No	Gewerbesitz lat
`office_lng`	No	Gewerbesitz lng
`attribution`	Yes	Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'
`google_maps`	No	'lat, lng'
`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.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / compact / description

Previous value: -"If true, omit h1/kicker/blurb/lage/geschichte — coords + URLs only."New value: +"If true, omit h1/kicker/blurb/lage/geschichte — coords + URLs + neighbors still present."

addedOutput schema / properties / maps_nav

Added value: +{
+  "description": "MAPS-IL1 mini-chrome URLs",
+  "properties": {
+    "buero": {
+      "format": "uri",
+      "type": "string"
+    },
+    "hub": {
+      "format": "uri",
+      "type": "string"
+    },
+    "mcp_hub": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / neighbors

Added value: +{
+  "description": "Up to 5 nearest Gebiete (slug/name/embed_map)",
+  "items": {
+    "properties": {
+      "embed_map": {
+        "format": "uri",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed9 schema fields changedSep 3, 2026

addedInput schema / properties / compact / description

Added value: +"If true, omit h1/kicker/blurb/lage/geschichte — coords + URLs only."

addedInput schema / properties / fields / description

Added value: +"Optional field filter: comma-separated names or array. Keeps envelope keys (ok, tool, summary, canonicalUrl, attribution, locale, related, count, total, offset, limit, compact) plus listed fields. Example: slug,name,plz,lat,lng."

addedInput schema / properties / locale / default
```
Added value: +"de"
```

addedInput schema / properties / locale / description

Added value: +"maps is German-only (de). Omit or pass de. Other values are ignored; URLs stay https://maps.ikeytz.com/… with no locale prefix. Not a www multi-locale switch — use @ikeytz/mcp list_locales on www for en|fr|ru|fa|ar|tr."

addedInput schema / properties / locale / enum
```
Added value: +[
+  "de"
+]
```

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"
+    },
+    "blurb": {
+      "description": "Short blurb when not compact",
+      "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"
+    },
+    "compact": {
+      "description": "Whether compact mode was applied",
+      "type": "boolean"
+    },
+    "embed_map": {
+      "format": "uri",
+      "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"
+    },
+    "geschichte": {
+      "description": "Geschichte text when not compact",
+      "type": "string"
+    },
+    "google_maps": {
+      "description": "'lat, lng'",
+      "type": "string"
+    },
+    "h1": {
+      "description": "Visitenkarte H1 when not compact",
+      "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"
+    },
+    "icbm": {
+      "description": "ICBM string",
+      "type": "string"
+    },
+    "kicker": {
+      "description": "Kicker when not compact",
+      "type": "string"
+    },
+    "kind": {
+      "description": "stadtteil | ort",
+      "type": "string"
+    },
+    "lage": {
+      "description": "Lage text when not compact",
+      "type": "string"
+    },
+    "lat": {
+      "description": "Place latitude",
+      "type": "number"
+    },
+    "lng": {
+      "description": "Place longitude",
+      "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": {
+      "description": "German name",
+      "type": "string"
+    },
+    "office_lat": {
+      "description": "Gewerbesitz lat",
+      "type": "number"
+    },
+    "office_lng": {
+      "description": "Gewerbesitz lng",
+      "type": "number"
+    },
+    "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"
+    },
+    "parent": {
+      "description": "Parent label",
+      "type": "string"
+    },
+    "plz": {
+      "description": "Postcode",
+      "type": "string"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "description": "Resolved 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"
+    },
+    "walkIn": {
+      "description": "Always false",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest — and it delivers: return payload shape (point card, maps_nav hub/buero/mcp-hub, 5 nearest neighbors by airline), conditional Lage texts suppressed by compact=true, field filtering semantics, the 52-area scope, single-lookup precedence, and the unknown_place error path. This is well beyond what the annotation provides.

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?

Tightly front-loaded with WHAT/RETURNS/USE/DOES NOT/NEXT labels and no filler, though the density borders on cryptic — tokens like 'MAPS-IL2' and '/mcp-hub' are opaque shorthand that cost a little readability.

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?

With an output schema present the description need not restate return values, yet its brief return summary, error-code contract, scope limit (52 areas, German-only) and tool chaining make it fully sufficient for correct invocation alongside a readOnly annotation.

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 description coverage is 100%, so a baseline of 3 applies, but the description adds genuine parameter behavior: the slug-first precedence when combined with plz/name, first-match-wins for shared PLZ values, and compact's effect on which keys survive. The only omission is that plz/name syntax detail lives in the schema rather than the description.

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 (fetch one Einsatzgebiet) and the exact resolution order (slug → plz first match → name substring), which immediately separates it from sibling lookups like find_by_plz, find_by_gebiet and list_service_areas. An agent can tell what this returns 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 Guidelines5/5

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

Explicit USE clause (user names a town/district in Landkreis Ludwigsburg), an explicit DOES NOT boundary (no geocoding of free addresses outside the 52), a defined failure mode (ok=false unknown_place), and a NEXT list routing to get_lage, get_geschichte, get_grenze, get_embed_map and distance_to_office. Alternatives and exclusions are both named.

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?