Gondola Award Travel Search
Server Details
Compare cash vs points on hotels, flights, and cars. Checkout supported hotels and rental cars.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 65.6% over 75 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- gondola-ai/gondola-mcp
- GitHub Stars
- 9
- Server Listing
- Gondola AI
TDQS
Scored across 43 tools
Most tools target clearly distinct resources and actions (book_flight/book_hotel/book_vehicle, search_flights/search_hotels/search_vehicles, cancel_flight_booking/cancel_vehicle_booking). However, the hotel pricing cluster (search_hotels, get_hotel_rates, compare_rates, get_multi_night_rates, diagnose_rates, predict_price, get_hotel_stats) has overlapping boundaries, and generic get_booking is ambiguous against get_flight_booking/get_vehicle_booking, though descriptions mostly disambiguate.
Names are overwhelmingly consistent snake_case verb_noun (search_*, get_*, book_*, cancel_*, create_/delete_rate_alert). Minor deviations like credit_card_coverage (noun phrase rather than verb_noun) and the generic get_booking keep it from perfect consistency, but the pattern remains predictable.
At 43 tools, this is a very heavy surface for a single MCP server. Even accounting for the broad travel domain (flights, hotels, cars, events, loyalty, alerts, profiles, diagnostics), many tools could be consolidated or scoped down, far exceeding the 3-15 well-scoped range.
Core search, booking, cancellation, and loyalty workflows are covered, including flight and vehicle cancellation. However, hotel booking has no corresponding cancel_hotel_booking tool, and there are no modify/change booking operations, leaving notable lifecycle dead ends despite the large tool count.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Removed
update_traveler_profile
1 tool update
- Changed
book_hotel1 field changed- changed
Input schema / properties / loyalty_account_id / descriptionPrevious value: -"Optional loyalty account ID to earn points and elite credit on this stay. Use the Member Number from get_loyalty_accounts that matches the booked hotel's chain (e.g. the World of Hyatt account for a Hyatt property)."New value: +"Optional loyalty account ID to earn points and elite credit on this stay. Use the Account ID from get_loyalty_accounts that matches the booked hotel's chain (e.g. the World of Hyatt account for a Hyatt property)."
1 tool update
- Added
get_favorite_hotels
1 tool update
- Changed
cancel_flight_booking2 fields changed- added
Input schema / properties / expected_ticket_settlement_affected_countAdded value: +{ + "description": "The exact affected ticket-document count from the preview. Required with expected_ticket_settlement_method; otherwise omit it.", + "type": "integer" +} - added
Input schema / properties / expected_ticket_settlement_methodAdded value: +{ + "description": "The exact ticket settlement method from the preview. Echo void when the preview advertises ticket settlement; otherwise omit it.", + "enum": [ + "void" + ], + "type": "string" +}
4 tool updates
- Added
book_flight - Added
cancel_flight_booking - Added
get_flight_booking - Added
prepare_flight_booking
1 tool update
- Changed
search_vehicles2 fields changed- added
Input schema / properties / dropoff_queryAdded value: +{ + "description": "Optional free-text drop-off location for a one-way rental, using the same formats as pickup_query. Omit for a round trip returning to the pickup location.", + "type": "string" +} - added
Input schema / properties / pickup_queryAdded value: +{ + "description": "Optional free-text pickup location: airport IATA, metro IATA, city, address, point of interest, or \"lat,lon\". When present, this takes precedence over pickup_location and includes both airport and city-desk inventory. Keep pickup_location populated as a compatible airport, metro, or city value.", + "type": "string" +}
1 tool update
- Changed
search_flights4 fields changed- changed
Input schema / properties / airlines / descriptionPrevious value: -"Optional airline codes or names, e.g. [\"UA\"] or [\"United\"]. Used only in \"browse\" mode to filter results."New value: +"Optional airline codes or names, e.g. [\"UA\"] or [\"United\"]. Filters the discovery results." - changed
Input schema / properties / max_stops / descriptionPrevious value: -"Optional maximum stops per direction in \"browse\" mode. Use 0 for nonstop only."New value: +"Optional maximum stops per direction. Use 0 for nonstop only." - removed
Input schema / properties / modeRemoved value: -{ - "default": "browse", - "description": "Leave as \"browse\" (default). \"book\" is a restricted alpha — only use it if the user explicitly asks to book a flight.", - "enum": [ - "browse", - "book" - ], - "type": "string" -} - changed
Input schema / properties / points / descriptionPrevious value: -"Set true when the traveler asks about award pricing, miles, points, redeeming rewards, award availability, or comparing cash vs. points — including phrases like \"include points\", \"show me miles\", \"how many points\", or \"use my [program] miles\". Default false. When true, award prices arrive on a follow-up call to get_flight_points (not in this response), so you MUST call get_flight_points after this returns. One-way flights only; no effect in book mode."New value: +"Set true when the traveler asks about award pricing, miles, points, redeeming rewards, award availability, or comparing cash vs. points — including phrases like \"include points\", \"show me miles\", \"how many points\", or \"use my [program] miles\". Default false. When true, award prices arrive on a follow-up call to get_flight_points (not in this response), so you MUST call get_flight_points after this returns. One-way flights only."
1 tool update
- Changed
search_flights1 field changed- changed
Input schema / properties / points / descriptionPrevious value: -"Leave as false (default). Set true only when the traveler asks about award pricing — redeeming miles or points, award availability, or whether cash or points is the better deal. Someone mentioning a balance in passing (\"I have 80k Aeroplan\") is context, not a request. Award prices are not in this response: they come from live airline scrapes, so a true here means you must make a second call to get_flight_points once this returns. Setting it speculatively costs the traveler that extra round trip. No effect in book mode."New value: +"Set true when the traveler asks about award pricing, miles, points, redeeming rewards, award availability, or comparing cash vs. points — including phrases like \"include points\", \"show me miles\", \"how many points\", or \"use my [program] miles\". Default false. When true, award prices arrive on a follow-up call to get_flight_points (not in this response), so you MUST call get_flight_points after this returns. One-way flights only; no effect in book mode."
1 tool update
- Changed
search_flights1 field changed- changed
Input schema / properties / airlines / descriptionPrevious value: -"Optional airline codes or names, e.g. [\"UA\"] or [\"United\"]. Used only in \"browse\" mode and passed to the Google Flights search API."New value: +"Optional airline codes or names, e.g. [\"UA\"] or [\"United\"]. Used only in \"browse\" mode to filter results."
2 tool updates
- Added
get_flight_points - Changed
search_flights1 field changed- added
Input schema / properties / pointsAdded value: +{ + "default": false, + "description": "Leave as false (default). Set true only when the traveler asks about award pricing — redeeming miles or points, award availability, or whether cash or points is the better deal. Someone mentioning a balance in passing (\"I have 80k Aeroplan\") is context, not a request. Award prices are not in this response: they come from live airline scrapes, so a true here means you must make a second call to get_flight_points once this returns. Setting it speculatively costs the traveler that extra round trip. No effect in book mode.", + "type": "boolean" +}
4 tool updates
- Changed
book_hotel1 field changed- changed
Input schema / properties / gondola_rate_id / descriptionPrevious value: -"The rate ID from get_hotel_details room rates."New value: +"The rate ID from get_hotel_rates room rates."
- Changed
get_booking_link1 field changed- changed
Input schema / properties / gondola_rate_id / descriptionPrevious value: -"Optional rate ID from get_hotel_details or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page."New value: +"Optional rate ID from get_hotel_rates or compare_rates. When provided, the link deep-links straight to that rate's checkout page instead of the generic hotel page."
- Changed
get_hotel_details4 fields changed- removed
Input schema / properties / checkinRemoved value: -{ - "description": "Check-in date in YYYY-MM-DD format.", - "type": "string" -} - removed
Input schema / properties / checkoutRemoved value: -{ - "description": "Check-out date in YYYY-MM-DD format.", - "type": "string" -} - removed
Input schema / properties / num_adultsRemoved value: -{ - "default": 2, - "description": "Number of adult guests.", - "type": "integer" -} - changed
Input schema / requiredPrevious value: -[ - "hotel_id", - "checkin", - "checkout" -]New value: +[ + "hotel_id" +]
- Added
get_hotel_rates
1 tool update
- Added
get_suite_upgrade_credits
4 tool updates
- Added
get_flight_credits - Changed
get_hotel_stats1 field changed- changed
Input schema / properties / nightly_cash_cost / descriptionPrevious value: -"The current nightly cash rate to score."New value: +"The current all-in nightly cash rate from search_hotels (stay total, including included taxes and fees, divided by nights)."
- Changed
get_similar_hotels1 field changed- added
Input schema / properties / destinationAdded value: +{ + "description": "Optional destination city or place for cross-city alternatives.", + "type": "string" +}
- Changed
predict_price1 field changed- changed
Input schema / properties / nightly_cash_cost / descriptionPrevious value: -"The current nightly cash rate to evaluate (from search_hotels)."New value: +"The current all-in nightly cash rate from search_hotels (stay total, including included taxes and fees, divided by nights)."
Related MCP Connectors
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Search and book flights and hotels: hundreds of airlines, plus bookable hotel rates.
Personal AI travel agent. Points optimization, live flight/hotel/award search, trip planning.
Live hotel and flight prices compared across Booking.com, Agoda, Trip.com and Traveloka, in USD.
Related MCP Servers
- AlicenseBqualityAmaintenanceOfficial MCP server for MAQAMI, a hotel and flight booking platform with 3M+ hotels. Search live hotel rates and flights, look up places, airports and hotel details, then prebook and book. Remote Streamable HTTP endpoint, no API key required.4186 npm2MIT
- FlicenseNot gradedqualityDmaintenanceOfficial Industry Standard MCP for Travel Awards, Points, and more. Search award flight availability across multiple airline loyalty programs, find sweet spots, check transfer partners, and get market stats all via MCP.1-
- AlicenseBqualityCmaintenanceEnables finding and comparing cash and award flights, with seat maps and trip planning, ranking options by user-defined per-mile valuations.6MIT
- FlicenseNot gradedqualityCmaintenanceEnables award flight search across 20+ airline programs using PointsYeah, with tools for comparing programs, estimating points value, and checking redemption deals.-
Glama MCP Gateway
Add one secure layer between your agents and this server.