ikeytz Einsatzgebiet-Karten

resolve_locale_url

Read-only

WHAT: path + locale → maps URL. maps is de-only: non-de requested still yields https://maps.ikeytz.com{path} with locale=de. Known Gebiet paths resolve to maps; unknown paths may www-pointer. REQUIRED path and locale. DOES NOT create /en on maps. NEXT: get_embed_map, www resolve_locale_url for marketing locales.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`path`	Yes	Required. Path starting with / (e.g. /pattonville) or a maps URL.
`locale`	Yes	Required. Only de is meaningful on maps; others ignored with a note.

Output Schema

TableJSON 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.
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`html`	No	Present when falling through to www pointer
`note`	No
`path`	No	Normalized path
`slug`	No	When a Gebiet matched
`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
`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.
`requested_locale`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 3, 2026

addedInput schema / properties / locale / description

Added value: +"Required. Only de is meaningful on maps; others ignored with a note."

addedInput schema / properties / path / description

Added value: +"Required. Path starting with / (e.g. /pattonville) or a maps URL."

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"
+    },
+    "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"
+    },
+    "html": {
+      "description": "Present when falling through to www pointer",
+      "type": "string"
+    },
+    "locale": {
+      "const": "de",
+      "type": "string"
+    },
+    "note": {
+      "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"
+    },
+    "path": {
+      "description": "Normalized path",
+      "type": "string"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "requested_locale": {
+      "type": "string"
+    },
+    "slug": {
+      "description": "When a Gebiet matched",
+      "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"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations provide readOnlyHint=true, but the description goes well beyond that by revealing non-obvious trap behaviors: maps is de-only, non-de locales still resolve to a de URL, unknown paths may return a www-pointer, and /en is never created. This gives an agent critical behavioral context that prevents incorrect assumptions about locale handling.

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?

The description is compact and information-dense, using labeled segments (WHAT, REQUIRED, DOES NOT, NEXT) that are easy to scan and front-loaded with the core purpose. The telegraphic style sacrifices some readability, but every segment earns its place by covering behavior, requirements, limitations, and next steps.

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?

Given the tool's two required parameters and the presence of an output schema, the description covers the important edge cases: de-only maps, unknown-path fallback, and the absence of /en creation. The phrase 'may www-pointer' leaves some ambiguity about the exact outcome for unknown paths, but the overall guidance is sufficient for correct invocation in most cases.

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% for both parameters, so baseline is 3. The description adds value by explaining that known Gebiet paths resolve to maps while unknown paths may yield a www-pointer, and it elaborates on locale behavior ('non-de requested still yields ... with locale=de'). This enriches the semantics beyond the schema's own descriptions.

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?

The description starts with 'WHAT: path + locale → maps URL', giving a clear transform and resource. It further clarifies the exact scope with 'maps is de-only' and 'Known Gebiet paths resolve to maps; unknown paths may www-pointer', so an agent can tell what the tool does. It does not explicitly differentiate from siblings like resolve_maps_url, but the behavior is clear enough.

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?

The description provides explicit situational guidance: 'non-de requested still yields ... with locale=de' and 'DOES NOT create /en on maps' tell the agent when this tool is not appropriate. The line 'NEXT: get_embed_map, www resolve_locale_url for marketing locales' points to alternatives, though 'www resolve_locale_url' is not a clearly named sibling, slightly reducing clarity.

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?