ikeytz Einsatzgebiet-Karten

Get Grenze Koordinaten

get_grenze_koordinaten

Read-only

WHAT: Full public Ort-Embed JSON for one Einsatzgebiet — same fields as GET https://maps.ikeytz.com/api/v1/embed/ort/{slug} (part=full): phone/NAP, style, point, featureCollection (Polygon+Punkt), OSM ids, embed paths (ort/grenze/punkt), iframe. Separate GeoJSON also at …/grenze and …/punkt; Sammel /api/v1/embed/orte/grenzen and /orte/punkte. No separate polygon/points keys (L-16). Lookup slug|plz|name. USE when the agent needs coordinates+boundary+NAP in one MCP call. DOES NOT change the HTTP embed API. DOES NOT replace slim get_grenze (polygon-only) or get_geo_api (URL pointers). NEXT: get_grenze, get_contact, get_embed_map.

Input 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

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.
`lat`	No
`lng`	No
`plz`	No
`via`	No
`hint`	No	Present when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
`href`	No	www keyword page
`icbm`	No
`name`	No
`part`	No	Always full
`slug`	No
`tool`	Yes	Echo of the tool name that produced this object (e.g. get_service_area).
`color`	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.
`phone`	No	NAP block (mobile, landline, fax, email, address, …)
`point`	No
`store`	No
`style`	No	MapLibre-ish style colors
`gruppe`	No
`iframe`	No
`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.
`points`	No	GeoJSON FeatureCollection
`polygon`	No	GeoJSON FeatureCollection (polygons only)
`purpose`	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.
`osmWayId`	No
`hasPolygon`	No
`attribution`	Yes	Required citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'
`countPoints`	No
`embedPublic`	No	Public relative embed path /api/v1/embed/ort/{slug}
`geoPosition`	No	lat;lng
`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.
`countPolygons`	No
`osmRelationId`	No
`hasPolygonKnown`	No
`featureCollection`	No	Polygon + point FeatureCollection

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 11, 2026

removedOutput schema / properties / embed

Removed value: -{
-  "description": "Relative fn embed path",
-  "type": "string"
-}

removedOutput schema / properties / embedGrenze
```
Removed value: -{
-  "type": "string"
-}
```

addedOutput schema / properties / embedPublic / description

Added value: +"Public relative embed path /api/v1/embed/ort/{slug}"

removedOutput schema / properties / embedPunkt
```
Removed value: -{
-  "type": "string"
-}
```

AddedSep 26, 2026

TDQS

A3.8/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 carries most of the load and does so reasonably: it discloses the exact returned field set, notes that separate GeoJSON exists at …/grenze and …/punkt, and points to Sammel endpoints. It confirms the read-only nature implicitly. It does not mention pagination, error behavior for unmatched lookups, or rate limits, which keeps it from a 5.

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?

The WHAT/USE/DOES NOT/NEXT scaffolding is a helpful structure, but the content is a wall of comma-chained fragments packed with internal references (L-16, "slim", NAC, Sammel) and multiple HTTP URLs. The key action is not front-loaded — the reader must parse the embed endpoint and field list before reaching the actual when-to-use sentence.

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?

An output schema exists, so return values need not be explained, yet the description still enumerates payload fields, which makes it largely complete for a 3-param, zero-required lookup tool. Coverage of the three lookup modes, precedence, and sibling routing is present. Only edge behavior (no match, ambiguous name matches) is unaddressed.

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 coverage is 100% and every parameter's description already covers lookup semantics, precedence (slug first), and PLZ collisions. The description adds only the compressed "Lookup slug|plz|name" restatement, which duplicates rather than extends the schema. Baseline 3 is correct when the schema does the heavy lifting.

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 that the tool returns the full public Ort-Embed JSON for one Einsatzgebiet, enumerating concrete payload fields (phone/NAP, style, point, featureCollection, OSM ids, embed paths, iframe). It also distinguishes itself from get_grenze (polygon-only) and get_geo_api (URL pointers). It falls short of a 5 because the name implies coordinates while the payload is a full embed object, and the purpose statement is wrapped around HTTP-path and internal-code jargon (L-16) that muddies the core claim.

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 when the agent needs coordinates+boundary+NAP in one MCP call" gives a clear trigger, and "DOES NOT replace slim get_grenze (polygon-only) or get_geo_api (URL pointers)" gives explicit exclusions with named alternatives. It stops short of 5 because the trailing "NEXT: get_grenze, get_contact, get_embed_map" list is unexplained and leaves the reader inferring why get_contact is a follow-up.

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?