ikeytz Einsatzgebiet-Karten

Get Geo Office

get_geo_office

Read-only

WHO/WHAT: Gewerbesitz (registered office) pin on maps.ikeytz.com/buero. walkIn=false always — mobile locksmith, not a shop counter. RETURNS street, postal, city, lat, lng, google_maps/icbm (same 'lat, lng' string), embed_map, geo_api (/api/v1/embed/office), note, walkIn, and einsatzgebiete (the same 52 name/slug/url links as the HTML list on /buero). USE for NAP/schema or Footer iframe. DOES NOT accept walk-in customers or bookings. The office is not a 53rd place. NEXT: get_contact, distance_to_office, get_business_identity, list_service_areas.

Input Schema

Name	Required	Description	Default
`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

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	Office latitude
`lng`	No	Office longitude
`city`	No	City
`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 (same as google_maps)
`note`	No	Büro · kein Kundenverkehr vor Ort
`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.
`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.
`postal`	No	Postal code
`street`	No	Office street
`walkIn`	No	Always false — no shop counter
`geo_api`	No	https://maps.ikeytz.com/api/v1/embed/office
`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.
`embed_map`	No	https://maps.ikeytz.com/buero
`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.
`einsatzgebiete`	No	Same 52 places as the /buero HTML list. Each item is name, slug, url.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / einsatzgebiete

Added value: +{
+  "description": "Same 52 places as the /buero HTML list. Each item is name, slug, url.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "format": "uri",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

Changed4 schema fields changedSep 21, 2026

addedOutput schema / properties / embed_map

Added value: +{
+  "description": "https://maps.ikeytz.com/buero",
+  "format": "uri",
+  "type": "string"
+}

addedOutput schema / properties / geo_api

Added value: +{
+  "description": "https://maps.ikeytz.com/api/v1/embed/office",
+  "format": "uri",
+  "type": "string"
+}

changedOutput schema / properties / icbm / description

Previous value: -"ICBM string"New value: +"ICBM string (same as google_maps)"

addedOutput schema / properties / note

Added value: +{
+  "description": "Büro · kein Kundenverkehr vor Ort",
+  "type": "string"
+}

Changed4 schema fields changedSep 3, 2026

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"
+]
```

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"
+    },
+    "city": {
+      "description": "City",
+      "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"
+    },
+    "google_maps": {
+      "description": "'lat, lng'",
+      "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"
+    },
+    "lat": {
+      "description": "Office latitude",
+      "type": "number"
+    },
+    "lng": {
+      "description": "Office 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"
+    },
+    "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"
+    },
+    "postal": {
+      "description": "Postal code",
+      "type": "string"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "street": {
+      "description": "Office street",
+      "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 — no shop counter",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With only readOnlyHint=true in annotations, the description carries most of the behavioral burden and does it well: it discloses that walkIn is always false, that the entity is a mobile locksmith rather than a counter, and that bookings are not supported. It stops short of noting e.g. caching or staleness of the pin data, but the core behavioral profile is clear.

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?

Front-loaded with WHO/WHAT, RETURNS, USE, DOES NOT, NEXT labels, so an agent can extract the needed line quickly. Slightly verbose in enumerating return fields that the output schema already covers, and "The office is not a 53rd place" is an opaque aside.

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?

A read-only single-parameter tool with an output schema is well covered: usage intent, exclusions, and routing are all present, so nothing critical is missing. The return-value listing is largely redundant given the output schema the agent already has.

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% – the single locale parameter is fully documented in the schema itself (German-only, ignored values, relation to www's list_locales). The description adds nothing about locale, 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 resource (Gewerbesitz / registered office pin at maps.ikeytz.com/buero) and a distinct scope, immediately separating it from sibling location tools by noting it is a mobile locksmith operation with walkIn=false always. An agent can distinguish this from distance_to_office or list_service_areas 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?

Contains explicit use cases ("USE for NAP/schema or Footer iframe"), explicit exclusions ("DOES NOT accept walk-in customers or bookings"), and a NEXT list routing the agent to get_contact, distance_to_office, get_business_identity, and list_service_areas for the adjacent needs.

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?