MCP proxy for mcp.tutu.ru that compacts always-loaded tool catalog descriptions and filters unreasonable responses; includes a harness to measure the impact
Assess whether a user request can be answered with the available tools or requires clarification
Check whether claims in an answer are grounded in the tool responses
Read-only per-car seat layout for a rail offer. Authoritative for any seat/car/gender/WC-distance question — if the offer has `details_ref`, CALL this rather than guessing; check `seatmap_status` (`ok` vs the rare `no_layout_for_carrier`). Prefer `task=` (`far_from_wc` / `female` / `together` / `summary`) for a short ranked answer over the whole train instead of paging every seat. Seat `type` is open vocabulary — match by PREFIX (`LOWER*`, `SIDE_LOWER*`), not equality. Join fares via `group_index` → `cars[].seat_groups[].fares[]`, not via `seat.type`. Seatmap prices are pre-cart and run below the final total (checkout adds ~6-8%) — quote the `search_rail` listing price as the bookable total. No window/aisle data exists in any car type. Gender: only `gender="FEMALE"`/`"MALE"` are proof of a gendered seat. Full pagination/`task=` reference and checkout handoff: `get_rail_instructions`.
Search Tutu hotel listings for a city and date range (`city_name` or `geo_id`). Each hotel carries `name`, `stars`, `rating`, `review_summary`, and `best_offer` — the cheapest rate of ONE room only (`price`, `offerpack_hash`, `checkout_url`); compare room categories via `get_offer_details`. `best_offer.price` is the TOTAL for the whole stay+guests (`price_basis="stay_total"`) — render as-is, never multiply by `stay.nights`. Grounding: ratings/amenities/quotes must come from `review_summary` / `get_offer_details`, never invented or substituted with generic praise. Before searching a broad request, ask 2-4 short clarifying questions (bed, breakfast, free-cancel, view) UNLESS the user already gave a deterministic pick rule ('дешевле', 'без уточнений') or explicit checkout intent — then search now and hand over the link in the same turn. Checkout: `best_offer.checkout_url` directly, or `create_checkout_link` with the row's `checkout_ref`; only a ROOM-level `offerpack_hash` (from `get_offer_details`) mints a cart, the listing one doesn't. Full field semantics: `get_hotels_instructions`.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 11 | <=2025-11-25 | v2 |
Search Russian Railways (РЖД) tickets between two cities. Each offer carries `price`, a `fares` summary (`{count, price_from, price_to, refundable_count, seat_categories, uncategorized_fares?}` — a count is a LOWER bound: `refundable_count: 0` means 'none confirmed refundable', not 'no refundable fare exists', and a `seat_categories` entry missing for сидячий/плацкарт/купе/СВ means not on sale ONLY when `uncategorized_fares` is absent), `legs[].segments[]` with carrier + train number + `vehicle_meta`, `search_results_url`, `checkout_url`, `checkout_ref`, and `details_ref` (→ `get_offer_details` for the full per-class ladder, → `get_rail_seatmap` for exact seats). Paginated: a page is a WINDOW over matched trains (`meta.total_matched`, `meta.has_more`) — never say a numbered train doesn't run from one page while `has_more` is true; pass `train_numbers` instead of paging blind. An empty `offers` with `meta.interchange_routes` populated means no DIRECT train that day; transfer plans are shown instead. Full field semantics, filter-interaction caveats and grounding rules: `get_rail_instructions`.