Российский сервис путешествий №1! Легко и удобно купить биле

Search hotels in a city (Tutu.ru)

Search Tutu hotel listings for a given city and date range. Resolve `city_name` (string) OR pass `geo_id` (Tutu internal). Returns hotels with `name`, `stars`, `rating`, `address`, `hotel_id` / `hotel_geo_id` (numeric id for get_offer_details), `tutu_offer_id` (listing UUID, not accepted by details), `review_summary` (when Tutu has reviews), `location`, `photos`, `best_offer` (`price` + `offerpack_hash` + `checkout_url` + `room_size_sqm` (room area in m² when Tutu wrote it in the room name, ofte

Search air tickets (Tutu.ru)

Search Tutu air tickets between two cities or specific airports. PRICE BASIS — every `price` already covers the WHOLE searched party (`adults` + `children` + `infants`; `meta.pricing.basis="party_total"`, verified live). Never multiply it by the passenger count. NB the sibling tools differ: `search_rail` / `search_etrain` quote ONE SEAT. `origin`/`destination` accept a city ('Москва'), an airport name ('Шереметьево') or a bare IATA code ('SVO', 'IST'). An airport input narrows the city-wide sear

Search railway tickets (Tutu.ru)

Search Russian Railways (РЖД) tickets between two cities. Returns the real departure & arrival station names per offer (useful when a city has several stations — Москва has Курский / Ленинградский / Казанский). `origin`/`destination` take a city or a station name (a station resolves when Tutu's index returns the station row, e.g. «Ярославский вокзал»; otherwise city-level). `meta.from/to` echo the resolved place (`name`, `geo_id`, `region`); `match` + `query` are added only when the resolved nam

Search bus tickets (Tutu.ru)

Search Tutu intercity bus tickets between two cities. Each offer carries: `price`, `variants[]` (where the carrier offers several tariffs), `legs[].segments[]` with stop names and carrier ratings in `review_summary` when Tutu returns feedback, and `search_results_url` (tutu.ru listing). Offers deliberately carry NO ready checkout link — the `explicit/bus` deeplink comes from `create_checkout_link(checkout_ref)`. `meta.from/to` echo the resolved place (`name`, `geo_id`, `region`); `match` + `quer

Search commuter trains (Tutu.ru)

Search Tutu suburban / commuter trains (электрички) between two cities. Useful for short routes around Москва / СПб / regional centres. `origin`/`destination` take a city or a station name (a station resolves when Tutu's index returns the station row, e.g. «Ярославский вокзал»; otherwise city-level). `meta.from/to` echo the resolved place (`name`, `geo_id`, `region`); `match` + `query` are added only when the resolved name differs from the wording sent (`lead` = a short form or typo read by Tutu

Compare all transport modes (Tutu.ru)

One-call multimodal 'how to get there' — runs avia + railway + bus + etrain in parallel and returns a unified sorted list under `variants[]`. PRICE BASIS — the modes do NOT agree on what a `price` covers: avia and bus quote the whole party, rail and etrain quote ONE SEAT (upstream never scales a train fare by the party). So with `adults` > 1 every variant also carries `price_party` — the comparable total for the searched party — and that is what the `price` ranking, `meta.modes_summary.<mode>.mi

Get offer details (Tutu.ru)

Fetch details for a single offer. Defaults to `view='compact'`: for hotels it caps photos, omits the per-rate `cancellation_policy` text (the `free_cancellation` / `free_cancellation_until` flags stay), omits room `amenity_groups` (flat `room_amenities` stays) and omits review TEXTS — the `review_summary` aggregate stays. Use `view='rules'` for the exact cancellation ladder, `view='reviews'` + `review_limit` for a feedback-only card (review texts with pagination; rooms collapse to stubs), or `vi

Get rail seat map (Tutu.ru)

Read-only per-car seat layout for a selected rail offer. Authoritative next step after `search_rail` for ANY question about exact seats, car layout, female/male/mixed compartments, lower/upper or nearby seats, or WC distance: if a rail offer has `details_ref`, CALL this — never tell the user the seat map is unavailable without calling, and read `seatmap_status` to tell a real layout (`ok`) from `no_layout_for_carrier`. Top-level `seatmap_status`: `"ok"` when Tutu returned a schema, `"no_layout_f

Avia search & checkout playbook (Tutu.ru)

Detailed avia playbook: airport disambiguation, airport-scoped search (origin/destination by airport name or IATA code), deeplink vs search-results checkout, fare-family override, baggage/refund grounding. Read before working with `search_avia` results.

Rail search, seat map & checkout playbook (Tutu.ru)

Detailed rail playbook: per-seat price basis (`price_party` for a party of 2+), `get_rail_seatmap` workflow (pagination, seat types, group_index join, per-group fare variants, focused `task=` queries incl. `together` for «места рядом», no-layout fallback), gender-coupe rules, `get_offer_details` and checkout (seat page vs straight-to-cart with chosen seats). Read before working with `search_rail` results.

Bus search & checkout playbook (Tutu.ru)

Detailed bus playbook: passengers (adults + children, whole-party pricing, composition in `checkout_ref`), stop presentation, `get_offer_details` (amenities/refund/luggage/seat_selection), checkout (seat page vs straight-to-cart with chosen seats) and grounding. Read before working with `search_bus` results.

Commuter-train search & checkout playbook (Tutu.ru)

Detailed etrain (commuter) playbook: per-seat price basis, `vehicle_meta` consist type, `get_offer_details` reformat, checkout and grounding. Read before working with `search_etrain` results.

Hotels search & details playbook (Tutu.ru)

Detailed hotels playbook: hotels-vs-transport `geo_id` pitfall, clarifying questions, `best_offer` vs `get_offer_details`, view/bed/breakfast grounding. Read before working with `search_hotels` results.

Multitransport compare playbook (Tutu.ru)

Detailed multitransport playbook: nested `variants[]`, per-mode price basis (compare on `price_party`, not `price`), `optimize_for`, per-mode soft-fail, and how checkout defers to the per-mode playbooks. Read before working with `search_multitransport` results.

Create a checkout link for a selected offer (Tutu.ru)

The single 'proceed to checkout' handle for a previously found offer. Call it as soon as the user commits to one option, however they word it — «беру», «самый быстрый из списка», «оформи», «забронируй», «дай ссылку» — and put the returned link in the same reply. It needs NO seat choice and NO passenger data in its default mode (the link opens the seat/room selection page). Pass the fields from the offer's `checkout_ref` object (emitted by every `search_hotels` / `search_avia` / `search_rail` / `

Register passenger(s) on a cart and get the pay link (Tutu.ru)

NOT the default booking handle — that is `create_checkout_link` («забронируй» included): normally hand the link first, offer this tool as the opt-in next step, and reach for it only when the user explicitly agrees to hand over passport data — never open the exchange by asking for documents, and never register before the user has confirmed the summary of what will be written. Register the passenger(s) the USER gave you (passport data) onto a Tutu checkout cart and return a `pay_url` — a hand-over

Fetch a tutu:// MCP resource by URI

Read a `tutu://` server resource and return its content. Use this when your MCP client doesn't auto-surface server resources in the prompt. Valid URIs: `tutu://help/overview` (full agent guide — start here), `tutu://geo` (city/point ids), `tutu://status` (server + upstream health), `tutu://special-offers` (experimental inspiration only). Returns `{uri, mime_type, content}`.