ikeytz Einsatzgebiet-Karten

Find By Geo

find_by_geo

Read-only

WHAT: Rank Einsatzgebiete by lat/lng (or icbm). Optional radius_km; else nearest N (limit, default 5). (0,0) and far points → ok=false outside_service_area. RETURNS items with distance_km. USE for 'near this coordinate'. DOES NOT route or drive-time. NEXT: get_service_area, get_grenze, distance_to_office.

Input Schema

Name	Required	Description
`lat`	No	WGS84 latitude. Required with lng unless icbm is set. (0,0) → outside_service_area.
`lng`	No	WGS84 longitude. Required with lat unless icbm is set.
`icbm`	No	ICBM or paste 'lat, lng' (comma-separated). Alternative to lat+lng.
`limit`	No	Maximum items or lines to return after offset. Omit = all remaining in the window (subject to tool-specific clamps). For geo near-search default is often 5 without radius_km, up to 52 with radius.
`radius_km`	No	Optional air-radius filter in km. Omit = return nearest N (limit). Far points / (0,0) → outside_service_area.

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	Query latitude
`lng`	No	Query longitude
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`icbm`	No	Query ICBM
`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	Ranked Gebiete with distance_km
`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.
`radius_km`	No	Applied radius or null
`nearest_km`	No	On outside_service_area failures: nearest distance if any
`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"
+}

Changed7 schema fields changedSep 3, 2026

addedInput schema / properties / icbm / description

Added value: +"ICBM or paste 'lat, lng' (comma-separated). Alternative to lat+lng."

addedInput schema / properties / lat / description

Added value: +"WGS84 latitude. Required with lng unless icbm is set. (0,0) → outside_service_area."

addedInput schema / properties / limit / description

Added value: +"Maximum items or lines to return after offset. Omit = all remaining in the window (subject to tool-specific clamps). For geo near-search default is often 5 without radius_km, up to 52 with radius."

addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedInput schema / properties / lng / description

Added value: +"WGS84 longitude. Required with lat unless icbm is set."

addedInput schema / properties / radius_km / description

Added value: +"Optional air-radius filter in km. Omit = return nearest N (limit). Far points / (0,0) → outside_service_area."

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"
+    },
+    "icbm": {
+      "description": "Query ICBM",
+      "type": "string"
+    },
+    "items": {
+      "description": "Ranked Gebiete with distance_km",
+      "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"
+    },
+    "lat": {
+      "description": "Query latitude",
+      "type": "number"
+    },
+    "lng": {
+      "description": "Query 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"
+    },
+    "nearest_km": {
+      "description": "On outside_service_area failures: nearest distance if any",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "radius_km": {
+      "description": "Applied radius or null",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "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.2/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 real additional weight: it discloses the error path ((0,0) and far points yield ok=false outside_service_area) and that results carry distance_km. That is meaningful behavior beyond the annotation, though it says nothing about ordering guarantees or how many results a radius query can return.

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?

What/Returns/Use/Does-not/Next structure is aggressively front-loaded and each clause carries information; nothing is padding. The terse label style still parses cleanly.

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?

An output schema exists and annotations cover the safety profile, so the description need not explain return payloads; it still adds the coordinate-alternative, default-limit behavior and error condition. The only residual gap is disambiguating this from find_by_icbm/find_by_gebiet for an agent choosing among near-identical siblings.

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 coverage is already 100%, so the schema defines lat, lng, icbm, limit and radius_km in full. The description restates the radius-vs-limit default (nearest N, default 5) rather than adding syntax or edge-case meaning not already present in the schema text, 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 and resource: rank Einsatzgebiete by lat/lng or icbm, with the exact filter semantics (radius_km vs nearest N). It also distinguishes itself from routing siblings by declaring 'DOES NOT route or drive-time,' so an agent can separate it from distance_to_office without opening a 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?

Gives an explicit trigger ('USE for near this coordinate'), an explicit exclusion (no routing/drive-time), and names follow-up tools (get_service_area, get_grenze, distance_to_office). It does not, however, clarify when to prefer this over the very similarly named find_by_icbm sibling, which remains an inference the agent must make.

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?