Vio.com

Fetch detailed information for hotels by ID. Use this to get data for specific hotel IDs from previous search results. Specify which data blocks to fetch (details, offers, rooms, reviews, etc.). Use the search tool for location-based discovery.

get_hotels

Search for hotels and accommodations by location, coordinates, or hotel ID. Pass any user-provided location/address/landmark to the query parameter - the geocoding service will resolve it. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"]. Place filter parameters inside the filters object. RESULT HANDLING: Results are ranked with best filter matches first. If filters cannot be fully satisfied, partial matches are returned. Always display results to the user immediately. Do NOT retry or paginate unless user explicitly requests more. When hasMoreResults=false, all matching hotels have been returned. UI UPDATE RULE: When a hotel UI widget is already displayed from a previous search, you MUST call this tool again for any user request that changes the search criteria (filters, dates, location, guests, sorting, etc.). Do NOT answer filter/refinement questions from memory or prior results - always call the tool to refresh the UI with updated results.

search_hotels

Discover WHEN to go — date-axis tool. Returns a price calendar of cheapest rates for each check-in date across a date range, so the user can pick the best dates to travel. Use this when the user is flexible on dates and wants to compare across them: "cheapest week in May", "price calendar for June", "when is Paris cheaper", "best dates to fly to Tokyo this fall", "should I go in May or June". Do NOT use this tool for: (a) fixed-date searches ("hotels in Paris for June 1-3") — use search_hotels; (b) "is this hotel a good deal?" / value or historical-trend questions — use search_hotels with include=["analytics"]; (c) hotel discovery / filtering by amenities or features — use search_hotels. IMPORTANT: hotel selection — by default we pick the top hotels by popularity, which gives a representative date trend across mainstream options but NOT the absolute floor. When the user asks for the cheapest possible trip ("cheapest", "lowest price", "willing to compromise on quality"), pass `sortField: "price"` with `sortOrder: "ascending"` so the calendar reflects the actual price floor, optionally with `filters.guestRating: [7, 8, 9, 10]` to keep quality reasonable. Without this the calendar can overstate prices by 30-90% on most dates. IMPORTANT: When query mentions "family" or "families", exclude hostels using filters.excludePropertyTypes: ["hostel"].

search_hotels_availability

Resolve a free-text location or hotel name into a ranked list of candidate hotels and places for disambiguation. Use this BEFORE search_hotels when a name could match more than one hotel or place (e.g. "the Hilton", "The Ritz", "Grand Hotel", "Springfield") to check whether it is unique or ambiguous. Each candidate includes its id, name, and placeDisplayName (location context, e.g. "Apollobuurt, Amsterdam, Netherlands") so you can tell same-named results apart. If exactly one hotel candidate clearly matches, proceed with its id via search_hotels or get_hotels. If several plausible candidates remain, ask the user which one they mean (cite the placeDisplayName) before continuing. If results are mostly places rather than hotels, ask the user for a destination. This tool does NOT return offers, pricing, or availability — it is only for resolving which hotel or place the user means. Pass only the name in query; put dates, party size, and filters on the search tools instead.

suggest_destinations