get_stop_realtime

Active

declared in 1.3.4

Returns live arrivals and vehicle positions for a stop, producing both a map UI block and a structured arrival list. Use this as the **default tool** when the user asks about arrivals, departures, or vehicles at a specific stop. Prefer `get_stop_geometry` when only static route polylines are needed and live data is irrelevant. Requires a numeric stop ID (shown on stop signage); use `get_stops_around_location` first if you only have an address or 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.50.

Parent server

mcp-lad-lviv-ua

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

2/7 registries

View full server →