Skip to main content
Glama

get_poi_details

Read-only

POI-Detail-Lookup per OSM-ID (Daten aus OpenStreetMap). Für „Öffnungszeiten von X", „erzähl mir was über X" ist dieses Werkzeug die Auskunft — erst verorten, dann abfragen: die osm_id stammt aus nearby/resolve_location/search_place. When to use: nach nearby / resolve_location / search_place lieferte einen POI mit osm_id und die Anfrage will Detail-Info — DE: „erzähl mir was über ", „was kostet der Eintritt", „Öffnungszeiten von ", „bei dem Wetter in unternehmen". EN: „tell me about ", „opening hours of ", „what can I do in given the weather". When NOT to use: für Stadt-/Region-IDs (nutze search_place); ohne vorherigen Tool-Call mit OSM-ID-Output (KEIN raten); wenn die Anfrage Routing/Abfahrten will (dafür der Server MobilityMCP). Required args: osm_id — die Zahl eines ids[]-Eintrags ("296222553") oder ein subject dieser Antwort ("node/296222553"). Optional osm_type ('node'/'way'/'relation' für osmNode/osmWay/osmRel); ohne Typ fragt die Zahl alle drei. Typical chain: TWO distinct chains feed this tool — (1) WETTER-CONTEXT: get_current_weather + nearby(node_types='poi') → THIS_TOOL ×3-5 (Trigger: „bei dem Wetter", „given the weather"). (2) REGION-TOURISM: search_place + resolve_location(node_types='poi') → THIS_TOOL ×3-5 (Trigger: „was kann ich in unternehmen" ohne Wetter-Bezug — dichtere OSM-Coverage über resolve_location). Multi-call: JA. Nach resolve_location/nearby mit N POI-Treffern: THIS_TOOL pro Top-3 bis Top-5 OSM-IDs PARALLEL aufrufen — jeder Call ist unabhängig, ein Burst ist erlaubt. NIE nur 1× rufen wenn N>1 POIs zurückkommen. Anti-Fab note: POI-Name, Operator, Öffnungszeiten, Adresse, Tags kommen AUSSCHLIESSLICH aus sources[].subjects[].properties dieses Aufrufs. sources: [] heißt: zu diesem Ort ist nichts abrufbar — so wiedergeben („Zu diesem Ort konnte ich aktuell keine Detail-Informationen abrufen"). OSM-Coverage: deutschlandweit; Tag-Dichte variiert je Region wie in OSM üblich. Shape: {osm_id, sources:[{source:'openstreetmap', subjects:[{subject, properties:{…raw OSM tags: name, tourism/historic/leisure, opening_hours, fee, website, wheelchair, addr:*…}, coord?:{lat,lon}}]}], facts?:{opening_hours?:{value,source}, price?:{free?,raw,source}}, ambiguous?}. coord (Geometrie-Mitte, additiv) steht je Subject NEBEN properties, wo das Element Geometrie hat. facts (additiv, top-level): normalisierte Öffnungszeiten + Preis mit Pro-Feld-Provenance (source:'openstreetmap') aus den opening_hours/fee-Tags — EINE stabile Stelle statt Roh-Tags durchwühlen. price.free=true bei fee=no (explizit „kostenlos"/Eintritt frei), false bei fee=yes/Betrag; price.raw trägt den Roh-Tag verbatim. Fehlt opening_hours UND fee → facts ABWESEND (honest, nie erfunden — Quellen-Priorität: kuratiert via get_tourism_details VOR diesem OSM-Bridge). ambiguous (additiv, true): nur ohne Typ — mehrere OSM-Objekte tragen die Nummer; dann fehlt facts, ein Wert gilt nur aus dem Subject, dessen name der gesuchte Ort ist (dessen subject als osm_id fragt eindeutig). attribution (additiv, top-level): die ODbL-Namensnennung der gelieferten OSM-Daten (ODbL) — {id:'ODbL-1.0', notice:'© OpenStreetMap contributors', url:'https://www.openstreetmap.org/copyright'}. EINMAL pro Antwort (nicht pro Treffer) und nur wenn sources nicht leer ist. Nennst du OSM-Daten in der Antwort, nenne die Quelle „OpenStreetMap" — die Lizenz-Auflage reist mit dem Tool-Output, nicht mit dem Prompt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "osm_id": "<osm_id>"
    },
    "name": "get_poi_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
osm_idYesAn `ids[]` value (`"296222553"`) or a `subject` of this tool's answer (`"node/296222553"`); a bare number without `osm_type` is asked for as all three types.
osm_typeNoThe type of a bare `osm_id`: `osmNode` → `node`, `osmWay` → `way`, `osmRel` → `relation`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / description
      Previous value: -"POI-detail lookup by OSM ID.\n\nAnswers with the OpenStreetMap record of that id: name, operator, the raw\ntags (`tourism`/`opening_hours`/`wheelchair`, …) and the geometry centre.\n`osm_id` is a bare numeric string (no `node:`/`way:`-prefix)."New value: +"POI-detail lookup by OSM element.\n\nAnswers with the OpenStreetMap record of that element: name, operator, the\nraw tags (`tourism`/`opening_hours`/`wheelchair`, …) and the geometry centre."
    • changedInput schema / properties / osm_id / description
      Previous value: -"Bare numeric OSM ID (e.g. `\"296222553\"` — no `node:` / `way:` prefix).\nMust match `^\\d+$` (validated at handler-time). The mcp-linking /\nmcp-geo callers already strip any type-prefix before exposing the\nvalue in `ids[].value`."New value: +"An `ids[]` value (`\"296222553\"`) or a `subject` of this tool's answer\n(`\"node/296222553\"`); a bare number without `osm_type` is asked for as\nall three types."
    • addedInput schema / properties / osm_type
      Added value: +{
      +  "description": "The type of a bare `osm_id`: `osmNode` → `node`, `osmWay` → `way`,\n`osmRel` → `relation`.",
      +  "enum": [
      +    "node",
      +    "way",
      +    "relation",
      +    null
      +  ],
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly/openWorld/non-destructive; the description goes far beyond by disclosing the empty-`sources` semantics (report honestly, never fabricate), `facts` absence when `opening_hours`/`fee` are missing, the `ambiguous` flag behavior, variable OSM tag density by region, and a licensing obligation (ODbL attribution once per response). These are exactly the behavioral traits annotations cannot carry.

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?

Front-loaded with purpose, then bolded "When to use"/"When NOT to use"/"Shape" blocks, so it is scannable despite its length. It is verbose and bilingual, and repeats the `osm_id` format already in the schema, which costs some density.

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?

With no output schema, the description fully documents the return envelope (`sources[].subjects[].properties`, `coord`, `facts`, `ambiguous`, `attribution`) including which fields are additive and when they are absent. For a 2-parameter open-world lookup feeding multi-call chains, nothing needed to invoke or interpret it is missing.

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 the schema text already documents that `osm_id` may be a bare number or `subject` and how `osm_node`/`way`/`relation` map. The description largely restates this, adding only the consequence that a bare number without `osm_type` triggers `ambiguous` — marginal added meaning over structured data.

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?

Opens with a specific verb+resource: "POI-Detail-Lookup per OSM-ID (Daten aus OpenStreetMap)", and immediately distinguishes itself from `search_place` (city/region IDs), MobilityMCP (routing), and `get_tourism_details` (curated source priority). An agent can tell exactly what it retrieves and from which data source without opening the 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?

Explicit "When to use" / "When NOT to use" blocks name the prerequisite tool calls (`nearby`, `resolve_location`, `search_place`) that supply the `osm_id`, forbid guessing without a prior OSM-ID output, and route routing requests elsewhere. Two concrete chains and multi-call burst guidance (Top-3 to Top-5 parallel) remove the usual ambiguity about call count.

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