ikeytz Einsatzgebiet-Karten

get_discovery

Read-only

WHAT: 1:1 mirror of a maps discovery file (UTF-8 text/JSON). which is required — common ids: ard, ai-catalog, ai-txt, ai-plugin, answer-engine, agent-skills, llms, llms-full, llms-index, llms-keywords, llms-serp, llms-impressum-kontakt, llms-orte-geo, llms-urheberrecht, llms-copyright, llms-mcp-server, llms-mcp-web, robots, sitemap-txt, sitemap-xml. Optional offset/limit line window. USE for agent-ready catalogs and robots/sitemap. DOES NOT invent missing files (missing=true). NEXT: find_by_keyword / find_by_serp for structured search; get_llms_txt / get_ai_txt aliases.

Input Schema

TableJSON Schema

Name	Required	Description
`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.
`which`	Yes	Required discovery id. Examples: ard, ai-catalog, ai-txt, ai-plugin, answer-engine, agent-skills, llms, llms-full, llms-index, llms-keywords, llms-serp, llms-impressum-kontakt, llms-orte-geo, llms-urheberrecht, llms-copyright, llms-mcp-server, llms-mcp-web, robots, sitemap-txt, sitemap-xml.
`offset`	No	0-based index into a list or discovery file lines (split on \n). 0 = first. Omit = 0. Combine with limit to page. Use nextOffset / offset+limit from a previous result when present.

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.
`body`	No	UTF-8 text window after offset/limit
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`path`	No	Public relative path of the file on maps
`text`	No	Alias/window of body when present
`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.
`limit`	No	Applied line limit, or null if omitted
`which`	No	Resolved discovery id (ard, ai-catalog, llms, robots, sitemap-txt, llms-mcp-server, …).
`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.
`offset`	No	Applied 0-based line offset
`missing`	No	true if the discovery file was not found on disk
`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'
`total_lines`	No	Line count of the full file
`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.

Changed8 schema fields changedSep 3, 2026

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 / offset / default
```
Added value: +0
```

addedInput schema / properties / offset / description

Added value: +"0-based index into a list or discovery file lines (split on \\n). 0 = first. Omit = 0. Combine with limit to page. Use nextOffset / offset+limit from a previous result when present."

addedInput schema / properties / offset / minimum
```
Added value: +0
```

addedInput schema / properties / which / description

Added value: +"Required discovery id. Examples: ard, ai-catalog, ai-txt, ai-plugin, answer-engine, agent-skills, llms, llms-full, llms-index, llms-keywords, llms-serp, llms-impressum-kontakt, llms-orte-geo, llms-urheberrecht, llms-copyright, llms-mcp-server, llms-mcp-web, robots, sitemap-txt, sitemap-xml."

removedInput schema / properties / which / enum

Removed value: -[
-  "llms",
-  "llms-full",
-  "llms-index",
-  "llms-keywords",
-  "llms-serp",
-  "llms-impressum-kontakt",
-  "llms-orte-geo",
-  "llms-urheberrecht",
-  "llms-copyright",
-  "llms-mcp-server",
-  "llms-mcp-web",
-  "robots",
-  "sitemap-txt",
-  "sitemap-xml",
-  "ai-txt",
-  "ai-plugin",
-  "answer-engine",
-  "ai-catalog",
-  "ard",
-  "agent-skills"
-]

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"
+    },
+    "body": {
+      "description": "UTF-8 text window after offset/limit",
+      "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"
+    },
+    "limit": {
+      "description": "Applied line limit, or null if omitted",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "missing": {
+      "description": "true if the discovery file was not found on disk",
+      "type": "boolean"
+    },
+    "offset": {
+      "description": "Applied 0-based line offset",
+      "type": "number"
+    },
+    "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": "Public relative path of the file on maps",
+      "type": "string"
+    },
+    "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"
+    },
+    "text": {
+      "description": "Alias/window of body when present",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Echo of the tool name that produced this object (e.g. get_service_area).",
+      "type": "string"
+    },
+    "total_lines": {
+      "description": "Line count of the full file",
+      "type": "number"
+    },
+    "which": {
+      "description": "Resolved discovery id (ard, ai-catalog, llms, robots, sitemap-txt, llms-mcp-server, …).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 3, 2026

changedInput schema / properties / which / enum

Previous value: -[
-  "llms",
-  "llms-full",
-  "llms-index",
-  "llms-keywords",
-  "llms-serp",
-  "llms-impressum-kontakt",
-  "llms-orte-geo",
-  "llms-urheberrecht",
-  "llms-copyright",
-  "llms-mcp-server",
-  "llms-mcp-web",
-  "robots",
-  "sitemap-txt",
-  "sitemap-xml",
-  "ai-txt",
-  "ai-plugin",
-  "answer-engine",
-  "ai-catalog",
-  "agent-skills"
-]New value: +[
+  "llms",
+  "llms-full",
+  "llms-index",
+  "llms-keywords",
+  "llms-serp",
+  "llms-impressum-kontakt",
+  "llms-orte-geo",
+  "llms-urheberrecht",
+  "llms-copyright",
+  "llms-mcp-server",
+  "llms-mcp-web",
+  "robots",
+  "sitemap-txt",
+  "sitemap-xml",
+  "ai-txt",
+  "ai-plugin",
+  "answer-engine",
+  "ai-catalog",
+  "ard",
+  "agent-skills"
+]

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true. The description adds value beyond that by disclosing the file format (UTF-8 text/JSON), the 1:1 mirror behavior, the optional offset/limit line window, and the behavior for missing files ('DOES NOT invent missing files (missing=true)'). This is solid supplemental behavioral context.

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 uses helpful labels (WHAT, USE, DOES NOT, NEXT) and is information-dense without being excessive. It repeats some examples already present in the schema, but the overall structure makes the key facts easy to scan.

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 retrieval tool with a fully documented schema, output schema, and readOnlyHint annotation, the description provides enough context: what the tool returns, when to use it, what it does not do, and which sibling tools to use next. Nothing critical is missing for correct invocation.

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 the schema already documents all three parameters thoroughly. The description adds a little context via 'which is required' and 'Optional offset/limit line window', but most parameter meaning is already in the schema, and the repeated id list does not add new parameter semantics.

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 ('get') and resource ('maps discovery file') and clearly describes a 1:1 mirror of that file. It lists concrete discovery ids and explicitly names sibling aliases (get_llms_txt / get_ai_txt), distinguishing this tool from related getters and structured-search tools.

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?

The description explicitly says 'USE for agent-ready catalogs and robots/sitemap' and directs to alternatives: 'NEXT: find_by_keyword / find_by_serp for structured search'. It also tells the agent that missing files are not invented, which helps decide when this tool is appropriate.

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?