ikeytz Einsatzgebiet-Karten

Get Ort Datetime

get_ort_datetime

Read-only

WHAT: Europe/Berlin wall clock to the second (stand YYYY-MM-DD HH:MM:SS CEST|CET) for pricing whenKey context. Optional slug|plz|name like get_service_area; omit = all 52 places with the same clock. RETURNS timezone, stand, iso, unix, date, time, tz, and whenKey day|night for www invoicing. USE before quoting via www get_invoice_line_items. DOES NOT return euro amounts (no price matrix on maps). NEXT: www @ikeytz/mcp get_invoice_line_items({situationKey, whenKey}) or get_prices.

Input Schema

TableJSON Schema

Name	Required	Description
`plz`	No	German postcode (PLZ). Several Gebiete can share one PLZ (e.g. 71638). For single lookup first match wins; use find_by_plz for all matches.
`name`	No	German place name substring (case-insensitive, umlauts ok), e.g. Grünbühl, Pattonville. Used when slug/plz omitted.
`slug`	No	URL slug of one of the 52 Einsatzgebiete, e.g. pattonville, bietigheim-bissingen, walheim, gruenbuehl. Matches https://maps.ikeytz.com/{slug}. Lookup order when combined with plz/name: slug first.

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.
`tz`	No	Abbreviation
`iso`	No	ISO-8601 with Berlin offset
`plz`	No	PLZ when resolved
`date`	No	YYYY-MM-DD in Berlin
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`name`	No	Place name when resolved
`slug`	No	Present when a place was resolved
`time`	No	HH:MM:SS in Berlin (24h)
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`unix`	No	Unix timestamp seconds
`count`	No	52 when listing all places
`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	All 52 slug/name/plz + clock when called without lookup
`stand`	No	Human clock 'YYYY-MM-DD HH:MM:SS CEST\|CET' Europe/Berlin to the second
`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.
`whenKey`	No	Price bucket for www get_invoice_line_items. day = Mo–Fr 08:00–17:59 Berlin except BW holidays; else night. Pass to www MCP — maps has no euro matrix.
`timezone`	No	Always Europe/Berlin
`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 / name / description

Added value: +"German place name substring (case-insensitive, umlauts ok), e.g. Grünbühl, Pattonville. Used when slug/plz omitted."

addedInput schema / properties / plz / description

Added value: +"German postcode (PLZ). Several Gebiete can share one PLZ (e.g. 71638). For single lookup first match wins; use find_by_plz for all matches."

addedInput schema / properties / slug / description

Added value: +"URL slug of one of the 52 Einsatzgebiete, e.g. pattonville, bietigheim-bissingen, walheim, gruenbuehl. Matches https://maps.ikeytz.com/{slug}. Lookup order when combined with plz/name: slug first."

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": {
+      "description": "52 when listing all places",
+      "type": "number"
+    },
+    "date": {
+      "description": "YYYY-MM-DD in Berlin",
+      "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"
+    },
+    "iso": {
+      "description": "ISO-8601 with Berlin offset",
+      "type": "string"
+    },
+    "items": {
+      "description": "All 52 slug/name/plz + clock when called without lookup",
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "date": {
+            "description": "YYYY-MM-DD in Berlin",
+            "type": "string"
+          },
+          "iso": {
+            "description": "ISO-8601 with Berlin offset",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "plz": {
+            "type": "string"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "stand": {
+            "description": "Human clock 'YYYY-MM-DD HH:MM:SS CEST|CET' Europe/Berlin to the second",
+            "type": "string"
+          },
+          "time": {
+            "description": "HH:MM:SS in Berlin (24h)",
+            "type": "string"
+          },
+          "timezone": {
+            "const": "Europe/Berlin",
+            "description": "Always Europe/Berlin",
+            "type": "string"
+          },
+          "tz": {
+            "description": "Abbreviation",
+            "enum": [
+              "CET",
+              "CEST"
+            ],
+            "type": "string"
+          },
+          "unix": {
+            "description": "Unix timestamp seconds",
+            "type": "number"
+          },
+          "whenKey": {
+            "description": "Price bucket for www get_invoice_line_items. day = Mo–Fr 08:00–17:59 Berlin except BW holidays; else night. Pass to www MCP — maps has no euro matrix.",
+            "enum": [
+              "day",
+              "night"
+            ],
+            "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"
+    },
+    "name": {
+      "description": "Place name when resolved",
+      "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"
+    },
+    "plz": {
+      "description": "PLZ when resolved",
+      "type": "string"
+    },
+    "related": {
+      "description": "Always includes https://maps.ikeytz.com/llms.txt.",
+      "items": {
+        "format": "uri",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "slug": {
+      "description": "Present when a place was resolved",
+      "type": "string"
+    },
+    "stand": {
+      "description": "Human clock 'YYYY-MM-DD HH:MM:SS CEST|CET' Europe/Berlin to the second",
+      "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"
+    },
+    "time": {
+      "description": "HH:MM:SS in Berlin (24h)",
+      "type": "string"
+    },
+    "timezone": {
+      "const": "Europe/Berlin",
+      "description": "Always Europe/Berlin",
+      "type": "string"
+    },
+    "tool": {
+      "description": "Echo of the tool name that produced this object (e.g. get_service_area).",
+      "type": "string"
+    },
+    "tz": {
+      "description": "Abbreviation",
+      "enum": [
+        "CET",
+        "CEST"
+      ],
+      "type": "string"
+    },
+    "unix": {
+      "description": "Unix timestamp seconds",
+      "type": "number"
+    },
+    "whenKey": {
+      "description": "Price bucket for www get_invoice_line_items. day = Mo–Fr 08:00–17:59 Berlin except BW holidays; else night. Pass to www MCP — maps has no euro matrix.",
+      "enum": [
+        "day",
+        "night"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool",
+    "attribution"
+  ],
+  "type": "object"
+}

First observedSep 1, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description usefully adds behavior: the default scope when all params are omitted ('all 52 places with the same clock') and a negative capability statement ('DOES NOT return euro amounts'). It also enumerates the returned fields, going beyond the read-only hint. It does not discuss error behavior or rate limits, but an output schema exists to carry 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with WHAT/RETURNS/USE/DOES NOT/NEXT labels, so the structure is scannable and nothing is padded. However, the telegraphic fragments and internal jargon ('whenKey', 'www invoicing', '@ikeytz/mcp') trade clarity for brevity, so conciseness comes at a readability cost rather than being cleanly efficient.

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?

For a read-only lookup with three optional params and an existing output schema, the description supplies the essentials: purpose, default scope, negative boundary, and next-step tools. An agent can call it correctly without opening the schema. It stops short of explaining how 'stand'/'whenKey' values should be consumed downstream, leaving a small gap.

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 already 100%, so the baseline is 3; the description adds genuine value by explaining the no-parameter default ('omit = all 52 places with the same clock') and by relating the three optional inputs to the sibling get_service_area. It correctly mirrors the slug/plz/name optionality rather than contradicting it.

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 states a specific verb+resource: it returns the Europe/Berlin wall-clock time to the second for a location ('Ort'), including the exact output format and the fields returned. It partially differentiates from siblings by pointing to get_service_area for the same slug/plz/name inputs and to get_invoice_line_items/get_prices as the follow-on tools. The phrasing is telegraphic ('for pricing whenKey context'), which slightly muddies an otherwise clear purpose.

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?

It gives explicit sequencing ('USE before quoting via www get_invoice_line_items') and an explicit exclusion ('DOES NOT return euro amounts'), plus NEXT-step alternatives (get_invoice_line_items or get_prices). That covers when-to-use, when-not, and alternatives, but the routing between the two named alternatives is not distinguished, and the internal shorthand reduces confidence.

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?