ikeytz Einsatzgebiet-Karten

List Nav

list_nav

Read-only

WHAT: maps navigation links — Hub, MCP, Urheberrecht, plus all 52 Gebiet URLs. USE to pick a maps page. DOES NOT include www header hubs (Preise/FAQ). NEXT: get_embed_map, get_page_summary.

Input Schema

TableJSON 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

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.
`note`	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	Nav links {label,url,slug?}
`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.
`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.

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"
+    },
+    "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"
+    },
+    "items": {
+      "description": "Nav links {label,url,slug?}",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "url": {
+            "format": "uri",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "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"
+    },
+    "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.1/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the safety profile is already covered and the bar is lower. The description adds real behavioral context: the exact content boundary (52 Gebiet URLs, excludes www header hubs), which tells the agent what will and will not appear in the result. No pagination or format notes, but the output schema presumably covers the return shape.

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?

The WHAT / USE / DOES NOT / NEXT structure is front-loaded and dense with zero filler — every clause carries selection-relevant information. Ideal size for a simple list tool.

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?

For a read-only listing tool with a fully documented single parameter and an existing output schema, this covers the essentials: what is listed, what is deliberately omitted, and what to call next. Nothing an agent needs to invoke it correctly is missing.

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% and the locale parameter is documented exhaustively in the schema itself (German-only, other values ignored, not a www multi-locale switch). The description says nothing about locale, so it neither adds nor detracts — baseline 3 for a schema that does all the work.

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 names a specific verb (maps/lists) and resource (navigation links) and enumerates concrete contents: Hub, MCP, Urheberrecht, and all 52 Gebiet URLs. It also scopes itself against adjacent concepts by excluding www header hubs (Preise/FAQ), though it stops short of naming the sibling tools (e.g. list_footer, get_hub) that cover that excluded ground.

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 to pick a maps page' gives a clear selection context, and the explicit exclusion of www header hubs is a genuine when-not statement. 'NEXT: get_embed_map, get_page_summary' signals a chaining pattern, though it does not say which tool handles the excluded Preise/FAQ cases, leaving one alternative unresolved.

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?