Skip to main content
Glama

ikeytz Einsatzgebiet-Karten

find_by_google_maps

Read-only

WHAT: Paste Google Maps / ICBM coordinates (q or icbm or lat/lng) → nearest ikeytz Gebiete (same ranking as find_by_geo). (0,0) → outside_service_area. USE when the user pastes a Maps pin. NEXT: get_service_area, get_embed_map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoPaste string containing 'lat, lng'
latNoWGS84 latitude. Required with lng unless icbm is set. (0,0) → outside_service_area.
lngNoWGS84 longitude. Required with lat unless icbm is set.
icbmNoICBM or paste 'lat, lng' (comma-separated). Alternative to lat+lng.
limitNoMaximum 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.
radius_kmNoOptional air-radius filter in km. Omit = return nearest N (limit). Far points / (0,0) → outside_service_area.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYestrue = use summary, canonicalUrl, and extra keys. false = do not invent data; read error + hint and retry with valid args or open hint.
latNo
lngNo
hintNoPresent when ok=false. Absolute URL or short recovery hint the agent should open or pass to another tool.
icbmNo
toolYesEcho of the tool name that produced this object (e.g. get_service_area).
countNo
errorNoPresent 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.
itemsNo
localeNoLocale actually used for URLs. maps is German-only: always de (MAPS-E8 — no /en on maps). Requested non-de is ignored; payload locale=de.
relatedNoAlways includes https://maps.ikeytz.com/llms.txt.
summaryNoPrimary text for the model. For discovery tools this is the file window. For list tools a compact one-liner. Quote with attribution.
radius_kmNo
nearest_kmNo
attributionYesRequired citation: 'Quelle: Schlüsseldienst Ludwigsburg ikeytz (ikeytz.com) · ai-train=no · https://maps.ikeytz.com/.well-known/ai.txt'
canonicalUrlNoBest 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.

  1. Changed8 schema fields changed
    • addedInput schema / properties / icbm / description
      Added value: +"ICBM or paste 'lat, lng' (comma-separated). Alternative to lat+lng."
    • addedInput schema / properties / lat / description
      Added value: +"WGS84 latitude. Required with lng unless icbm is set. (0,0) → outside_service_area."
    • 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 / lng / description
      Added value: +"WGS84 longitude. Required with lat unless icbm is set."
    • addedInput schema / properties / q / description
      Added value: +"Paste string containing 'lat, lng'"
    • addedInput schema / properties / radius_km / description
      Added value: +"Optional air-radius filter in km. Omit = return nearest N (limit). Far points / (0,0) → outside_service_area."
    • 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"
      +    },
      +    "icbm": {
      +      "type": "string"
      +    },
      +    "items": {
      +      "items": {
      +        "additionalProperties": true,
      +        "description": "One Einsatzgebiet point card (not a polygon).",
      +        "properties": {
      +          "distance_km": {
      +            "description": "Present on geo-ranked results: air distance from query point",
      +            "type": "number"
      +          },
      +          "embed_map": {
      +            "description": "https://maps.ikeytz.com/{slug}",
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "geo_api": {
      +            "description": "https://maps.ikeytz.com/api/v1/embed/ort/{slug}",
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "google_maps": {
      +            "description": "Paste-ready 'lat, lng'",
      +            "type": "string"
      +          },
      +          "icbm": {
      +            "description": "ICBM 'lat, lng' (same as google_maps)",
      +            "type": "string"
      +          },
      +          "kind": {
      +            "description": "stadtteil | ort",
      +            "type": "string"
      +          },
      +          "lat": {
      +            "description": "WGS84 latitude of THIS place",
      +            "type": "number"
      +          },
      +          "lng": {
      +            "description": "WGS84 longitude of THIS place",
      +            "type": "number"
      +          },
      +          "maps_mcp": {
      +            "const": "https://maps.ikeytz.com/mcp",
      +            "description": "maps MCP endpoint",
      +            "format": "uri",
      +            "type": "string"
      +          },
      +          "name": {
      +            "description": "German place name",
      +            "type": "string"
      +          },
      +          "parent": {
      +            "description": "Ludwigsburg or Landkreis Ludwigsburg",
      +            "type": "string"
      +          },
      +          "plz": {
      +            "description": "Postcode",
      +            "type": "string"
      +          },
      +          "slug": {
      +            "description": "maps slug",
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "Keyword/www page URL when present",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "lat": {
      +      "type": "number"
      +    },
      +    "lng": {
      +      "type": "number"
      +    },
      +    "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"
      +    },
      +    "nearest_km": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "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"
      +    },
      +    "radius_km": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "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"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the special (0,0) → outside_service_area behavior and the ranking equivalence with find_by_geo. This gives agents useful behavioral context for interpreting results that annotations alone do not provide.

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 description is compact and well-structured with 'WHAT:', 'USE when', and 'NEXT:' labels. Every sentence earns its place, front-loading the core action before edge cases and suggested follow-ups.

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?

Given a fully documented schema and an output schema, the description covers the key usage context, special-case behavior, and next steps. Its only minor gap is not disambiguating from find_by_icbm when raw ICBM coordinates are pasted, but it is otherwise complete for the stated Maps pin scenario.

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%, so the description is not burdened with documenting parameters. It does restate the q/icbm/lat/lng alternatives in prose, but adds minimal new meaning beyond the schema's own parameter descriptions.

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: 'Paste Google Maps / ICBM coordinates' yields 'nearest ikeytz Gebiete'. It also distinguishes itself by noting the same ranking as find_by_geo and the (0,0) edge case, making it clear which coordinate-paste scenario this tool handles.

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?

The description explicitly says 'USE when the user pastes a Maps pin', providing a clear trigger condition. It does not, however, explicitly state when not to use it or compare to closely related siblings like find_by_icbm or find_by_geo beyond the ranking note.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources