zingbus

Call this when the customer is ready to book a specific trip. On MCP Apps hosts it renders an interactive picker (boarding point, dropping point, seats) beneath your reply. Three ways to call it: (1) `tripToken` only — picker with ALL available seats. (2) `tripToken` + `seatNumbers` WITHOUT boarding/dropping — when you've already narrowed the seats to a shortlist for the user's request (e.g. 'cheapest sleeper', 'window seats'), pass just those seat labels; the picker then shows ONLY those seats so your filtering carries into the widget instead of being redundant. Exclude gender-reserved seats (isFemaleReserved/isMaleReserved) from the shortlist — the picker won't offer them anyway. (3) `tripToken` + `boardingStation` + `droppingStation` + `seatNumbers` — a full selection that builds the checkout link (the picker calls this on Continue; you may too if the user gave exact values). Prefer (1) or (2) and let the user finish in the picker — don't ask for boarding/dropping points yourself. Keep your reply to a short lead-in line; the picker renders below it, so do NOT list the points or seats in text. In modes (1)/(2) the response has `awaitingSelection: true` (and boardingPoints/droppingPoints/seats). This is the NORMAL 'picker is shown' state — it is NOT a failure. Do NOT tell the user checkout failed or that the bus/seat/points are unavailable; just present the picker and let them choose. Only in mode (3) does the response carry `checkoutReady`: when true it includes a `checkoutUrl` (a safe redirect link with no internal IDs — share it verbatim, never modify or invent one); when false, relay any `warnings` and help the user adjust, and don't share a link.

prepare_checkout

Find available zingbus trips between two cities on a date. Call this whenever the user wants to travel and has given an origin, destination, and date. zingbus operates only within India, so both cities must be Indian cities. If either city is outside India, don't call this — tell the user zingbus serves only cities within India and ask for an Indian origin/destination.Each trip in the result has a `tripToken` — remember it and pass it to get_trip / prepare_checkout to act on that trip (do not show it to the user).Each trip has three fare fields: quote `payableFare` to the user (the final price, already discounted). `originalFare` is the pre-discount price (show it struck-through if you like, never as the price to pay). `discountAmount` = originalFare − payableFare.

search_buses

Get full details and current seat availability for one trip. Call after search_buses when the user wants more detail on a specific option (exact times, fare, bus type, seats left). Pass the `tripToken` of the trip the user picked (from search_buses). This is read-only/informational — it does NOT start a booking; when the user is ready to book, call prepare_checkout. The response contains: `seats` (per-seat list with deck, type, `seatPosition` window/aisle, availability and fare — show which seats are open and their price). Seats with `isFemaleReserved` or `isMaleReserved` = true are reserved for that gender; since this flow never collects the traveller's gender, do NOT recommend or shortlist those — only offer seats where both flags are false, `boardingPoints` and `droppingPoints` (pickup/drop options — present these by name), `fromCity`/`toCity`/`tripToken` (keep the tripToken for the follow-up prepare_checkout call; do NOT show it to the user). Each seat's `fare` has `originalFare` / `payableFare` / `discountAmount` — quote `payableFare` as the seat price.

get_trip