Pricewin Hotels & Flights

STEP 2 OF 2 for cancelling a booking — IRREVERSIBLE. Call this only after request_cancel_token (step 1) has emailed the guest a token AND the guest has pasted that token back to you. Never invent, guess, or reuse a token: it comes from the guest's email and works once. BEFORE calling, confirm with the guest — in their own language — the booking being cancelled and the refund they will receive (use get_cancellation_policy for the exact terms), and get an explicit yes. If the user asks to cancel but you have no token yet, call request_cancel_token instead. On success the booking is cancelled and any refund is initiated.

cancel_booking

Check whether the hotel has confirmed a booking request yet. Use it when the guest asks what happened to a request they already sent. Requires the confirmationCode returned by request_booking.

check_booking_status

Fetch the structured cancellation policy for a specific rate plan so a guest can see accurate refund terms. Use propertyId from search results and ratePlanId from get_hotel_detail roomTypes[].ratePlanId. Pass checkInDate (YYYY-MM-DD) to compute the exact free-cancellation deadline. Returns the non-refundable flag, free-cancellation window, refund percentage, a human-readable summary, and the computed deadline.

get_cancellation_policy

Get prices and availability for an OpenTravel direct-listed hotel over a specific date range, alongside its photo gallery, amenities and room types. Requires check-in and check-out dates; get_hotel_info covers the same hotel without dates when the question is about facilities, photos, room size or policies rather than price. Use it for a result with source 'OPENTRAVEL_DIRECT'; pass its propertyId UUID when available. hotelName plus city is a fallback only for a property already known to be an OpenTravel direct listing. Returns a markdown summary and structured detail.

get_hotel_detail

Static facts about an OpenTravel direct-listed hotel, with no check-in or check-out date required: photo gallery, property description, address, facilities (parking, pool, pets and so on), check-in and check-out times, the house cancellation policy, and each room type's description, floor area, capacity, photos and in-room facilities. Carries no prices and no availability — get_hotel_detail covers those for a specific date range. Takes the propertyId UUID from search results.

get_hotel_info

Retrieve the latest results for a flight search session started by search_flights_live. Results may be partial while the search continues; call again every few seconds until status is 'completed' or 'failed'.

poll_flight_results

Retrieve the latest results for a hotel search session started by search_hotels_live. Results may be partial while the search continues; call again every few seconds until status is 'completed'. Returns hotel listings including direct-booking OpenTravel properties with their propertyId for use with get_hotel_detail.

poll_search_results

STEP 1 OF 2 for cancelling a booking. Call this when the user asks to cancel ('hủy đặt phòng', 'cancel my booking', 'tôi muốn hủy phòng'). It emails a single-use cancel token to the address on the booking; nothing is cancelled yet and nothing is charged or refunded by this call. You need the confirmationCode and the guest email that matches the booking — ask the user for whichever is missing before calling. Before calling, it is good practice to call get_cancellation_policy so the guest knows the refund terms first. After it succeeds, tell the guest to check their email; they either click the link or paste the token back to you, and then you call cancel_booking (step 2). The token expires in 24 hours and works once.

request_cancel_token

Sends a booking REQUEST to the hotel. Nothing is charged and NO ROOM IS HELD — the hotel confirms the request, and the guest pays at the property on arrival. Tell the guest plainly that no room is held yet and that the hotel will confirm by email. NO PAYMENT EXISTS ON THIS ROAD. Never ask how the guest wants to pay, and never state, repeat, summarise or promise a payment method, QR code, transfer, card, PayPal, payment link or deposit — not even one the guest named earlier in this chat, in an earlier chat, or that you remember about them. There is nothing to choose and nothing to send: any payment method on screen here is wrong and misleads the guest about how they will pay. There is also no LATER payment step: do not say payment will come once the booking is confirmed. The guest pays at the property on arrival, and that is the end of it. Relay the tool's reply as it is written rather than summarising it — the two facts it leads with, that no room is held and nothing has been charged, are the ones guests act on. Guest details left out of the call come back in the result as the question to put to the guest. Several rooms of the same room type are ONE request: set roomCount and call this tool once — calling it once per room creates separate requests, each with its own code, that the hotel handles separately. Only rooms of different room types need separate calls. check_booking_status takes the confirmationCode it returns.

request_booking

Search flights for a route and date with real-time fares from Agoda, Trip.com and Google Flights. Returns a session ID immediately while the search runs; call poll_flight_results to retrieve results. Prefer the language field for widget localization. AIRPORT CODES: origin and destination must be 3-letter IATA codes — convert city names yourself before calling (Sài Gòn/Ho Chi Minh City → SGN, Hà Nội → HAN, Đà Nẵng → DAD, Nha Trang → CXR, Phú Quốc → PQC). If a city has more than one airport, ask the user which one. DATES: never guess. Turn any relative phrase ('tuần sau', 'next month') into exact dates, state them back to the user, and search only once they confirm.

search_flights_live