get_stop_geometry

Active

declared in 1.3.4

Returns static map context for a stop: its marker and polylines for every route that serves it. No live data is fetched. Use this when you need to enrich an existing map with route shapes (e.g. overlay polylines alongside a `get_stop_realtime` map block) or when the user asks to visualise which routes pass a stop without needing live arrivals. Do NOT use this when live arrival times or vehicle positions are needed — use `get_stop_realtime` instead. Requires a numeric stop ID; call `get_stops_around_location` first if you only have coordinates.

Parameters schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "stop_id"
  ],
  "properties": {
    "stop_id": {
      "anyOf": [
        {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "Positive integer stop code (e.g. 707).",
          "exclusiveMinimum": 0
        },
        {
          "type": "string",
          "pattern": "^\\d+$",
          "description": "Stop code as a digits-only string (e.g. \"707\")."
        }
      ],
      "description": "Municipal stop code shown on stop signage (e.g. 707). Accepts a positive integer or an equivalent digit-only string."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.70.

Parent server

mcp-lad-lviv-ua

https://github.com/vbhjckfd/timetable-api-node

2/7 registries

View full server →