ikeytz Einsatzgebiet-Karten

Find By Google Maps

find_by_google_maps

Read-only

WHAT: Paste Google Maps / ICBM coordinates (q or icbm or lat/lng) → nearest ikeytz Gebiete (same ranking as find_by_geo). (0,0) → outside_service_area. USE when the user pastes a Maps pin. NEXT: get_service_area, get_embed_map.

Input Schema

Name	Required	Description
`q`	No	Paste string containing 'lat, lng'
`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
`lng`	No
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`icbm`	No
`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.
`radius_km`	No
`nearest_km`	No
`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"
+}

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

Added value: +"Paste string containing 'lat, lng'"

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": {
+      "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"
+    },
+    "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"
+    },
+    "nearest_km": {
+      "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": {
+      "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?

readOnlyHint=true already declares the safety profile, so the bar is lower. The description still adds real behavior beyond annotations: the (0,0) → outside_service_area sentinel and the shared ranking with find_by_geo. It stops short of stating output shape or fallback behavior when a pin is far outside the service area.

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?

Three telegraphic clauses with WHAT/USE/NEXT labels, front-loaded and free of filler. Every sentence carries a distinct piece of operational information.

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, so return values need not be explained. Input alternatives, the out-of-area sentinel, and next-step tools are all covered; the only remaining gap is differentiation from the overlapping find_by_icbm sibling.

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 baseline is 3. The description restates the accepted input forms ('q or icbm or lat/lng') and the (0,0) sentinel, but that information is already fully in the schema, and it adds no new constraint (e.g., which form takes precedence) beyond what is documented there.

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 ('Paste ... coordinates → nearest ikeytz Gebiete') and anchors the ranking to a sibling ('same ranking as find_by_geo'), so an agent can tell it apart from the geo/icbm finders. The WHAT label makes the purpose scannable.

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 when the user pastes a Maps pin' gives an explicit triggering condition, and 'NEXT: get_service_area, get_embed_map' routes follow-up. However it does not disambiguate from the sibling find_by_icbm, which the description openly overlaps with ('Google Maps / ICBM coordinates ... or icbm').

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?