ikeytz Einsatzgebiet-Karten

Get Ratgeber

get_ratgeber

Read-only

WHAT: Returns only a URL to www /ratgeber/{slug} — not the article body. slug required. USE when the user names a Ratgeber slug on maps. Prefer list_ratgeber for the hub link when the slug is unknown; prefer www MCP get_ratgeber for fulltext. DOES NOT return article text.

Input Schema

Name	Required	Description	Default
`slug`	Yes	Required Ratgeber slug
`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.
`npm`	No	www CLI package @ikeytz/mcp
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`html`	No	Absolute www.ikeytz.com URL — open there or call @ikeytz/mcp
`note`	No	maps only points; Volltext/Preise/FAQ live on www
`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.
`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.
`www_mcp`	No	https://www.ikeytz.com/mcp — sister machine for prices/FAQ/corpus
`www_tool`	No	Same tool name on www MCP that holds the real payload
`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	Locale the caller asked for; maps still returns locale=de

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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"
+]
```
addedInput schema / properties / slug / description
```
Added value: +"Required Ratgeber slug"
```

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": "Absolute www.ikeytz.com URL — open there or call @ikeytz/mcp",
+      "format": "uri",
+      "type": "string"
+    },
+    "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": {
+      "description": "maps only points; Volltext/Preise/FAQ live on www",
+      "type": "string"
+    },
+    "npm": {
+      "description": "www CLI package @ikeytz/mcp",
+      "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"
+    },
+    "requested_locale": {
+      "description": "Locale the caller asked for; maps still returns locale=de",
+      "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"
+    },
+    "www_mcp": {
+      "description": "https://www.ikeytz.com/mcp — sister machine for prices/FAQ/corpus",
+      "format": "uri",
+      "type": "string"
+    },
+    "www_tool": {
+      "description": "Same tool name on www MCP that holds the real payload",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

readOnlyHint=true already declares the safe-read profile, but the description adds real value by disclosing what the response actually contains and, more importantly, what it does not ('Returns only a URL ... not the article body', 'DOES NOT return article text'). That output-shape constraint is the key behavioral fact an agent needs and is not derivable from the annotations. It stops short of mentioning auth, rate limits, or cross-domain redirect behavior, so a 4 rather than 5.

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 front-loaded clauses labeled WHAT / USE / DOES NOT, with zero filler. The most decision-relevant facts (URL-only, slug required, alternatives) all appear before the reader has to hunt.

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?

With an output schema present, the description is not obliged to document the return value, yet it still states that the result is a URL rather than article text, which is the fact most likely to surprise a caller. Combined with the named alternatives, an agent has everything needed to select and invoke it. Minor remaining gap: no note on whether the slug must exist or what happens on an unknown slug.

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 schema itself is unusually rich (the locale description spells out the de-only enum, the ignored-values behavior, and the cross-reference to www list_locales). The description only restates 'slug required', which the schema already marks as required, so it adds no meaning beyond the structured fields. 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?

The description states a specific verb and resource ('Returns only a URL to www /ratgeber/{slug}') and immediately scopes the output by excluding the article body. It also explicitly distinguishes itself from the siblings list_ratgeber and the www MCP get_ratgeber, so an agent can route without opening any 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?

It gives a positive trigger ('USE when the user names a Ratgeber slug on maps') and two named alternatives with the conditions that select them: list_ratgeber for the hub link when the slug is unknown, and www MCP get_ratgeber for fulltext. Nothing is left to inference.

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?