get_stops_around_location

Active

declared in 1.3.4

Discovers transit stops near a geographic point, returning each stop's numeric code, name, coordinates, and walking distance. Also emits a map UI block with multiple markers for map-capable clients (e.g. ChatGPT). Use this as the **first step** whenever the user provides an address, place name, or coordinates and you need stop IDs before calling `get_stop_realtime` or `get_stop_geometry`. Do NOT use this to fetch arrivals or live vehicle data — it returns stop metadata only. Default radius is 1 000 m; narrow it (e.g. 300 m) for dense urban areas or widen it (up to 3 000 m) for rural locations.

Parameters schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "latitude",
    "longitude"
  ],
  "properties": {
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Decimal latitude of the search centre, WGS84 (e.g. 49.842 for central Lviv)."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Decimal longitude of the search centre, WGS84 (e.g. 24.031 for central Lviv)."
    },
    "radius_meters": {
      "type": "integer",
      "maximum": 3000,
      "minimum": 50,
      "description": "Search radius in metres (50–3000, default 1000). Use ~300 for dense urban intersections, up to 3000 for suburban or rural areas."
    }
  }
}

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 →