PriceWin Travel Search
Use only the tools of the pricewin MCP server (https://mcp.price.win/mcp,
installed with the web-data/pricewin MCP component). Agents prefix them with the server name — for
example mcp__pricewin__search_hotels_live — and the steps below use the bare
tool names. Do not replace them with browser automation, shell commands, direct
API calls, or invented booking URLs.
All prices are in USD.
Collect the required trip details
For a hotel search, obtain:
- destination or city;
- check-in and check-out dates;
- number of adults, defaulting to 2 when the user does not specify;
- number of rooms, defaulting to 1.
For a flight search, obtain:
- origin and destination airport IATA codes;
- departure date and optional return date;
- number of adults, defaulting to 1;
- cabin, defaulting to economy.
Resolve unambiguous relative dates from the current date. Ask one concise
follow-up when a required date, destination, or airport is genuinely ambiguous.
Never invent a date or silently choose among multiple plausible airports.
Pass language matching the user's language when supported. Do not put
unrelated conversation or personal data in queryText.
Search hotels
- Call
search_hotels_live with the destination, dates, occupancy, and only
the filters the user actually requested.
- Read
sessionId and nights from the response.
- Call
poll_search_results with that sessionId and nights.
- If the response is pending or partial with no useful results, poll again
until results arrive, the search completes or fails, or the session expires.
- Present a concise comparison of relevant results. Label the source and
currency exactly as returned.
Use hotelName, area, priceMin, or priceMax only when the user supplied
that constraint. Do not claim that a result is the cheapest in the whole
market; describe it as the cheapest among the sources returned for this search.
A failed or missing source does not invalidate results from other sources.
Look up one named hotel
When the user names a single hotel rather than a city, call
get_ota_hotel_detail with hotelName and its city (or the Booking.com
propertyUrl from an earlier result) and the user's dates. It returns that
hotel's rooms, live prices, facilities and reviews from Booking.com.
Inspect an OpenTravel direct hotel
Call get_hotel_detail only for a hotel identified as an OpenTravel direct
listing.
- Prefer its
propertyId from opentravelResults.
- Reuse the user's dates and occupancy.
- Use
hotelName plus city only when the property is already known to be an
OpenTravel direct listing and no propertyId is available.
- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.
Present the returned photos, amenities, availability, room capacity, total
price, per-night price, and currency without changing their meaning. State
clearly when availability or a price is missing.
Answer a question about a hotel
For questions about a hotel itself — check-in and check-out times, facilities,
photos, description, room types — call get_hotel_info with the propertyId
of an OpenTravel direct listing, usually from opentravelResults of a search
already made. It needs no dates and returns no prices or availability; for
those, use get_hotel_detail. When the property has not published a field,
say so rather than filling it in.
Explain a cancellation policy
Call get_cancellation_policy only after get_hotel_detail supplies both:
- the property's
propertyId; and
- the selected room's
ratePlanId.
Pass the check-in date so the tool can compute an exact deadline. Report the
returned non-refundable status, refund percentage, free-cancellation window,
deadline, and summary. Never infer a policy or deadline when the tool does not
return one.
Search flights
- Call
search_flights_live with IATA codes, departure date, optional return
date, adults, and cabin.
- Read the returned
sessionId.
- Call
poll_flight_results with that sessionId.
- Continue only until useful results arrive, the search completes or fails, or
the session expires.
- Present relevant options with source, carrier, times, stops, cabin, currency,
and fare exactly as returned.
Keep outbound and return legs distinct. Each leg is a separate one-way ticket
with its own booking link: when you pair an outbound and a return flight, give
the total as the sum of the two fares and say that each leg is booked
separately. Never present a pair as one round-trip ticket, and do not imply that
a fare is still available after the live result expires.
Request a booking at an OpenTravel direct hotel
Only an OpenTravel direct listing can be booked this way; an Agoda,
Booking.com or Traveloka result cannot, and the user follows its own link
instead.
- Call
request_booking with the propertyId, roomTypeId, dates and the
guest's name, phone number and email. Ask for whichever of those three is
missing; they go to the hotel, which needs them to honour the reservation.
- Relay the tool's reply as written. The two facts it leads with — that no
room is held and that nothing has been charged — are the ones the guest
acts on.
- Keep the
confirmationCode it returns; check_booking_status reads the
request's state back with it.
There is no payment step, now or later. Never ask how the guest wants to pay,
and never mention a card, transfer, QR code, payment link or deposit — not
even one the guest named earlier. The guest pays the property on arrival.
Cancel a booking
- Call
get_cancellation_policy first, with the propertyId, ratePlanId
and check-in date of the booked room, and tell the guest what they will get
back — or that the property has published no policy.
- Call
request_cancel_token with the confirmation code and the email on the
booking. This cancels nothing; it emails a single-use token.
- Ask the guest to paste the token from that email. Never invent, guess or
reuse one.
- Confirm the booking and the refund amount with the guest in their own
language, get an explicit yes, then call
cancel_booking with the code,
the token and the guest's reason.
cancel_booking cannot be undone. If there is no token yet, the answer is
step 2, never step 4.
Safety and output rules
- Use only these twelve tools:
search_hotels_live, poll_search_results,
search_flights_live, poll_flight_results, get_ota_hotel_detail,
get_hotel_detail, get_hotel_info, get_cancellation_policy,
request_booking, check_booking_status, request_cancel_token, and
cancel_booking.
- Treat all prices as time-sensitive and avoid guarantees or unsupported
"lowest price" claims.
- Use only outbound URLs returned by the tools. Never construct, append,
rewrite, or guess a booking URL.
- Collect the guest's name, phone and email only to send a booking request,
and only when the guest is actually sending one. Never ask for card data,
bank details, credentials, or any other payment information: no tool here
accepts them, and no step of this skill takes money.
- Do not modify an existing booking. There is no tool for it; a change means
cancelling and sending a new request, and saying so plainly.
- If a tool fails, state the limitation briefly and suggest a new search. Do
not fabricate partial inventory, prices, availability, or policies.
1---2name: pricewin-travel-search3description: Search and compare live hotel and flight prices with the PriceWin MCP server, look up one named hotel, inspect OpenTravel direct listings, send a booking request to a partner hotel (no payment; the guest pays at the property), and cancel one. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect a hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.4metadata:5 source: https://skillmd.com/skills/davila7/pricewin-travel-search6---789# PriceWin Travel Search1011Use only the tools of the `pricewin` MCP server (`https://mcp.price.win/mcp`,12installed with the `web-data/pricewin` MCP component). Agents prefix them with the server name — for13example `mcp__pricewin__search_hotels_live` — and the steps below use the bare14tool names. Do not replace them with browser automation, shell commands, direct15API calls, or invented booking URLs.1617All prices are in USD.1819## Collect the required trip details2021For a hotel search, obtain:2223- destination or city;24- check-in and check-out dates;25- number of adults, defaulting to 2 when the user does not specify;26- number of rooms, defaulting to 1.2728For a flight search, obtain:2930- origin and destination airport IATA codes;31- departure date and optional return date;32- number of adults, defaulting to 1;33- cabin, defaulting to economy.3435Resolve unambiguous relative dates from the current date. Ask one concise36follow-up when a required date, destination, or airport is genuinely ambiguous.37Never invent a date or silently choose among multiple plausible airports.3839Pass `language` matching the user's language when supported. Do not put40unrelated conversation or personal data in `queryText`.4142## Search hotels43441. Call `search_hotels_live` with the destination, dates, occupancy, and only45 the filters the user actually requested.462. Read `sessionId` and `nights` from the response.473. Call `poll_search_results` with that `sessionId` and `nights`.484. If the response is pending or partial with no useful results, poll again49 until results arrive, the search completes or fails, or the session expires.505. Present a concise comparison of relevant results. Label the source and51 currency exactly as returned.5253Use `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied54that constraint. Do not claim that a result is the cheapest in the whole55market; describe it as the cheapest among the sources returned for this search.56A failed or missing source does not invalidate results from other sources.5758## Look up one named hotel5960When the user names a single hotel rather than a city, call61`get_ota_hotel_detail` with `hotelName` and its `city` (or the Booking.com62`propertyUrl` from an earlier result) and the user's dates. It returns that63hotel's rooms, live prices, facilities and reviews from Booking.com.6465## Inspect an OpenTravel direct hotel6667Call `get_hotel_detail` only for a hotel identified as an OpenTravel direct68listing.6970- Prefer its `propertyId` from `opentravelResults`.71- Reuse the user's dates and occupancy.72- Use `hotelName` plus `city` only when the property is already known to be an73 OpenTravel direct listing and no `propertyId` is available.74- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.7576Present the returned photos, amenities, availability, room capacity, total77price, per-night price, and currency without changing their meaning. State78clearly when availability or a price is missing.7980## Answer a question about a hotel8182For questions about a hotel itself — check-in and check-out times, facilities,83photos, description, room types — call `get_hotel_info` with the `propertyId`84of an OpenTravel direct listing, usually from `opentravelResults` of a search85already made. It needs no dates and returns no prices or availability; for86those, use `get_hotel_detail`. When the property has not published a field,87say so rather than filling it in.8889## Explain a cancellation policy9091Call `get_cancellation_policy` only after `get_hotel_detail` supplies both:9293- the property's `propertyId`; and94- the selected room's `ratePlanId`.9596Pass the check-in date so the tool can compute an exact deadline. Report the97returned non-refundable status, refund percentage, free-cancellation window,98deadline, and summary. Never infer a policy or deadline when the tool does not99return one.100101## Search flights1021031. Call `search_flights_live` with IATA codes, departure date, optional return104 date, adults, and cabin.1052. Read the returned `sessionId`.1063. Call `poll_flight_results` with that `sessionId`.1074. Continue only until useful results arrive, the search completes or fails, or108 the session expires.1095. Present relevant options with source, carrier, times, stops, cabin, currency,110 and fare exactly as returned.111112Keep outbound and return legs distinct. Each leg is a separate one-way ticket113with its own booking link: when you pair an outbound and a return flight, give114the total as the sum of the two fares and say that each leg is booked115separately. Never present a pair as one round-trip ticket, and do not imply that116a fare is still available after the live result expires.117118## Request a booking at an OpenTravel direct hotel119120Only an OpenTravel direct listing can be booked this way; an Agoda,121Booking.com or Traveloka result cannot, and the user follows its own link122instead.1231241. Call `request_booking` with the `propertyId`, `roomTypeId`, dates and the125 guest's name, phone number and email. Ask for whichever of those three is126 missing; they go to the hotel, which needs them to honour the reservation.1272. Relay the tool's reply as written. The two facts it leads with — that no128 room is held and that nothing has been charged — are the ones the guest129 acts on.1303. Keep the `confirmationCode` it returns; `check_booking_status` reads the131 request's state back with it.132133There is no payment step, now or later. Never ask how the guest wants to pay,134and never mention a card, transfer, QR code, payment link or deposit — not135even one the guest named earlier. The guest pays the property on arrival.136137## Cancel a booking1381391. Call `get_cancellation_policy` first, with the `propertyId`, `ratePlanId`140 and check-in date of the booked room, and tell the guest what they will get141 back — or that the property has published no policy.1422. Call `request_cancel_token` with the confirmation code and the email on the143 booking. This cancels nothing; it emails a single-use token.1443. Ask the guest to paste the token from that email. Never invent, guess or145 reuse one.1464. Confirm the booking and the refund amount with the guest in their own147 language, get an explicit yes, then call `cancel_booking` with the code,148 the token and the guest's reason.149150`cancel_booking` cannot be undone. If there is no token yet, the answer is151step 2, never step 4.152153## Safety and output rules154155- Use only these twelve tools: `search_hotels_live`, `poll_search_results`,156 `search_flights_live`, `poll_flight_results`, `get_ota_hotel_detail`,157 `get_hotel_detail`, `get_hotel_info`, `get_cancellation_policy`,158 `request_booking`, `check_booking_status`, `request_cancel_token`, and159 `cancel_booking`.160- Treat all prices as time-sensitive and avoid guarantees or unsupported161 "lowest price" claims.162- Use only outbound URLs returned by the tools. Never construct, append,163 rewrite, or guess a booking URL.164- Collect the guest's name, phone and email only to send a booking request,165 and only when the guest is actually sending one. Never ask for card data,166 bank details, credentials, or any other payment information: no tool here167 accepts them, and no step of this skill takes money.168- Do not modify an existing booking. There is no tool for it; a change means169 cancelling and sending a new request, and saying so plainly.170- If a tool fails, state the limitation briefly and suggest a new search. Do171 not fabricate partial inventory, prices, availability, or policies.