Chelaile (车来了) MCP

Get a city's runtime config: max poll interval and "arriving" time threshold.

This is mostly relevant if you are deciding how aggressively to refresh — not for end-user questions about lines or stops.

Args:

• city_id (string, required): e.g. '034' (Shanghai), '027' (Beijing)
• response_format ('markdown' | 'json')

Returns (json): { "maxInterval": 30, "arrivingStationLimitSeconds": 180, "busDisplayConfig": { "lineDetail": "time#order#distance", "other": "time#order" } }

Returns a line's name, first and last bus, price and station count, its full ordered station list, the reverse-direction line ID, and every bus currently on it.

Canonical "when will my bus arrive" tool. Returns every bus currently on the line, with the nearest one carrying an ETA to the waiting stop.

Important: the upstream predicts an ETA for only the nearest bus heading to your stop. Buses farther up the route are returned (with position/speed/capacity) but their eta field is null. That's not a bug.

Args:

• city_id (string, required)
• line_id (string, required): from bus_search
• target_order (string, required): the waiting stop's order on the line. Source: bus_get_line_detail.stations[i].order, or bus_get_nearby_stops.stops[].lines[].targetOrder.
• station_id (string, required): sId of the waiting stop
• lat / lng (string, required): WGS-84 — the user's location is best; if unavailable, use the waiting stop's wgsLat/wgsLng (from line_detail.stations[i]).
• response_format ('markdown' | 'json')

Returns (json): { "line": { "lineId":"...", "name":"71", "direction":0, "endSn":"..." }, "targetOrder": 2, "realData": true, "buses": [ { "busId":"...", "licence":"...", "order":2, "lat":..., "lng":..., "speed":5.7, "capacity":0, "distanceToWaitStn":90, "eta":{"travelTime":25,"arrivalTime":1779070466055,"displayTime":"10:14"} }, { "busId":"...", "order":3, "lat":..., "lng":..., "speed":3, "capacity":0, "eta":null }, ... ], "note": "..." }

Field notes:

• The 'line' sub-object intentionally omits startSn — upstream does not return it on this endpoint. Read it from bus_get_line_detail if needed.
• eta.travelTime is seconds remaining
• eta.arrivalTime is a ms timestamp
• eta.displayTime is a "HH:MM" hint from upstream
• capacity: 0=light, 1=moderate, 2=crowded

Polyline coordinates for drawing a line on a map. Points with 'stopOrder' are actual stops; others are shape points between stops.

Args:

• city_id (string, required)
• line_id (string, required)
• include_shape (boolean, default false): false returns only stop markers (~25 points); true returns all shape points (~400-500). Skip unless you actually need to draw the line.
• response_format ('markdown' | 'json')

Returns (json): { "pointCount": 480, // total shape points upstream returned "stopCount": 23, // stop markers among them "points": [{ "lat":..., "lng":..., "stopOrder":1 }, ...] } 'points' is the filtered list — stops only by default, full polyline when include_shape=true.

Known caveat: upstream sometimes omits the terminus stop from the polyline, so 'stopCount' may be one less than bus_get_line_detail's 'stationsNum' (e.g. 23 vs 24). Trust bus_get_line_detail for the authoritative station list; line_route is just for drawing.

Markdown mode only summarises counts; request JSON to read coordinates.

Resolves an approximate location from the caller's public IP, accurate to the city rather than the street.

Lists bus stops near a WGS-84 coordinate, each annotated with the lines that pass through and the buses approaching.

Returns a stop's exact coordinates, every line through it with first bus, last bus and price, the buses in realtime, and the metro lines nearby.

Per-trip departure schedule for a line. The upstream returns one of three modes via mode:

• 'scheduled' (timeTableType=1): an explicit timetable array of trips
• 'interval' (timeTableType=2): the line runs at a fixed headway — NO per-trip times are returned
• 'special' / 'unknown' (timeTableType=3 or other)

Most lines in Shanghai are 'interval', so this tool is rarely the right one. To answer "first/last bus", "is the line still running", or "what's the next departure", call bus_get_line_detail instead — it always returns firstTime / lastTime / price / live buses.

Args:

• city_id (string, required)
• line_id (string, required)
• line_no (string, required): rider-facing short name from bus_search.lines[].name (e.g. '71'). Do NOT pass the internal lineNo like 'r95817'.
• direction ('0'|'1'): the line direction
• response_format ('markdown' | 'json')

Returns (json): { "line": { "lineId":"...", "name":"71", "direction":0, "startSn":"...", "endSn":"..." }, "timeTableType": 2, "mode": "interval", "timetable": null, "note": "This line runs at a fixed interval — ..." }

Lists the cities covered by the realtime bus data service — by default the upstream's curated hot set, or the full list when asked for it.

Returns the one or two imminent buses heading to an anchor stop, with an ETA and the next stop name.

Plans bus and metro routes between two GCJ-02 points and returns alternatives sorted by recommendation, each split into walking and ride segments.

Refresh realtime bus info for several (line, stop) pairs in one round-trip. Useful for a 'favourites' dashboard.

Args:

• city_id (string, required)
• line_stn (string, required): semicolon-separated quadruples Format: lineId,stopId,nextId,targetOrder;lineId,stopId,nextId,targetOrder;... 'nextId' may be empty between the two commas.
• response_format ('markdown' | 'json')

Example: '21283603183,021-15232,,2;21283604388,021-8685,,4'

Returns (json): { "lines": [ { "line": { "lineId":"...", "name":"71", "direction":0, "endSn":"..." }, "depDesc": "...", "buses": [ { "busId":"...", "order":2, "capacity":0, "distanceToDest":881, "eta":{"travelTime":221,"arrivalTime":...} } ] } ] }

Soft cap: up to 10 quadruples per call.

Converts WGS-84 coordinates into a Chinese postal address with province, city, district and township.

Searches inside a city by keyword and returns the matching lines, stations and POIs in one call.

Paginated 'see more' for one category from bus_search.

Args:

• city_id (string, required)
• keyword (string, required): same keyword used in bus_search
• type ('1'|'2'|'3'): 1=more lines, 2=more stations, 3=more POIs (default '1')
• response_format ('markdown' | 'json')

Returns: same shape as bus_search but only the requested category is populated.