Update to Pricewin Hotels & Flights
Snapshot Oct 24, 2026 · 12:58 UTC · version 2.0.0
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for pricewin-travel-search
Full description — Now says: 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...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Full description
Sep 30, 2026 · 22:58 UTC
including hotel details and cancellation terms for OpenTravel direct listings. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect an OpenTravel hotel or room, or check a selected rate's cancellatio...
Oct 24, 2026 · 12:58 UTC
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 an Ope...
Skill instructions
Sep 30, 2026 · 22:58 UTC
including hotel details and cancellation terms for OpenTravel direct listings. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect an OpenTravel hotel or room, or check a selected rate's cancellatio...
Oct 24, 2026 · 12:58 UTC
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 an Ope...
Supporting files
Sep 30, 2026 · 22:58 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":525}]
Oct 24, 2026 · 12:58 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":599}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,6 +1,6 @@ --- name: pricewin-travel-search -description: Search and compare live hotel and flight prices with the Pricewin MCP server, including hotel details and cancellation terms for OpenTravel direct listings. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect an OpenTravel hotel or room, or check a selected rate's cancellation policy. +description: Search and compare live hotel and flight prices with the Pricewin MCP server, 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 an OpenTravel hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way. --- # Pricewin Travel Search @@ -63,6 +63,15 @@ 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: @@ -87,24 +96,62 @@ 5. Present relevant options with source, carrier, times, stops, cabin, currency, and fare exactly as returned. -Keep outbound and return legs distinct. Do not combine unrelated one-way fares -into a round trip or imply that a fare is still available after the live result -expires. +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. + +1. 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. +2. 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. +3. 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 + +1. 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. +2. Call `request_cancel_token` with the confirmation code and the email on the + booking. This cancels nothing; it emails a single-use token. +3. Ask the guest to paste the token from that email. Never invent, guess or + reuse one. +4. 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 six tools: `search_hotels_live`, `poll_search_results`, - `search_flights_live`, `poll_flight_results`, `get_hotel_detail`, and - `get_cancellation_policy`. +- Use only these eleven tools: `search_hotels_live`, `poll_search_results`, + `search_flights_live`, `poll_flight_results`, `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. -- Explain that booking and payment happen outside ChatGPT on Pricewin or the - selected travel provider. -- Do not ask for or handle guest names, email addresses, booking references, - card data, credentials, or other booking/payment information. -- Do not create, modify, cancel, or pay for a booking. Those actions are not - exposed by this plugin. +- 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 plugin 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.
Full technical diff · 3 changed fields
changed /description
"Search and compare live hotel and flight prices with the Pricewin MCP server, including hotel details and cancellation terms for OpenTravel direct listings. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect an OpenTravel hotel or room, or check a selected rate's cancellation policy."
"Search and compare live hotel and flight prices with the Pricewin MCP server, 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 an OpenTravel hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way."
changed /included_files
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 525
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 599
}
]changed /skill_md_contents
"---\nname: pricewin-travel-search\ndescription: Search and compare live hotel and flight prices with the Pricewin MCP server, including hotel details and cancellation terms for OpenTravel direct listings. Use when the user asks to find hotels or flights for dates, compare travel prices, inspect an OpenTravel hotel or room, or check a selected rate's cancellation policy.\n---\n\n# Pricewin Travel Search\n\nUse only the Pricewin MCP dependency declared in `agents/openai.yaml`. Do not\nreplace it with browser automation, shell commands, direct API calls, or\ninvented booking URLs.\n\n## Collect the required trip details\n\nFor a hotel search, obtain:\n\n- destination or city;\n- check-in and check-out dates;\n- number of adults, defaulting to 2 when the user does not specify;\n- number of rooms, defaulting to 1.\n\nFor a flight search, obtain:\n\n- origin and destination airport IATA codes;\n- departure date and optional return date;\n- number of adults, defaulting to 1;\n- cabin, defaulting to economy.\n\nResolve unambiguous relative dates from the current date. Ask one concise\nfollow-up when a required date, destination, or airport is genuinely ambiguous.\nNever invent a date or silently choose among multiple plausible airports.\n\nPass `language` matching the user's language when supported. Do not put\nunrelated conversation or personal data in `queryText`.\n\n## Search hotels\n\n1. Call `search_hotels_live` with the destination, dates, occupancy, and only\n the filters the user actually requested.\n2. Read `sessionId` and `nights` from the response.\n3. Call `poll_search_results` with that `sessionId` and `nights`.\n4. If the response is pending or partial with no useful results, poll again\n until results arrive, the search completes or fails, or the session expires.\n5. Present a concise comparison of relevant results. Label the source and\n currency exactly as returned.\n\nUse `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied\nthat constraint. Do not claim that a result is the cheapest in the whole\nmarket; describe it as the cheapest among the sources returned for this search.\nA failed or missing source does not invalidate results from other sources.\n\n## Inspect an OpenTravel direct hotel\n\nCall `get_hotel_detail` only for a hotel identified as an OpenTravel direct\nlisting.\n\n- Prefer its `propertyId` from `opentravelResults`.\n- Reuse the user's dates and occupancy.\n- Use `hotelName` plus `city` only when the property is already known to be an\n OpenTravel direct listing and no `propertyId` is available.\n- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.\n\nPresent the returned photos, amenities, availability, room capacity, total\nprice, per-night price, and currency without changing their meaning. State\nclearly when availability or a price is missing.\n\n## Explain a cancellation policy\n\nCall `get_cancellation_policy` only after `get_hotel_detail` supplies both:\n\n- the property's `propertyId`; and\n- the selected room's `ratePlanId`.\n\nPass the check-in date so the tool can compute an exact deadline. Report the\nreturned non-refundable status, refund percentage, free-cancellation window,\ndeadline, and summary. Never infer a policy or deadline when the tool does not\nreturn one.\n\n## Search flights\n\n1. Call `search_flights_live` with IATA codes, departure date, optional return\n date, adults, and cabin.\n2. Read the returned `sessionId`.\n3. Use `poll_flight_results` when the host exposes it to the model; otherwise\n let the Pricewin flight widget perform its app-side polling.\n4. Continue only until useful results arrive, the search completes or fails, or\n the session expires.\n5. Present relevant options with source, carrier, times, stops, cabin, currency,\n and fare exactly as returned.\n\nKeep outbound and return legs distinct. Do not combine unrelated one-way fares\ninto a round trip or imply that a fare is still available after the live result\nexpires.\n\n## Safety and output rules\n\n- Use only these six tools: `search_hotels_live`, `poll_search_results`,\n `search_flights_live`, `poll_flight_results`, `get_hotel_detail`, and\n `get_cancellation_policy`.\n- Treat all prices as time-sensitive and avoid guarantees or unsupported\n \"lowest price\" claims.\n- Use only outbound URLs returned by the tools. Never construct, append,\n rewrite, or guess a booking URL.\n- Explain that booking and payment happen outside ChatGPT on Pricewin or the\n selected travel provider.\n- Do not ask for or handle guest names, email addresses, booking references,\n card data, credentials, or other booking/payment information.\n- Do not create, modify, cancel, or pay for a booking. Those actions are not\n exposed by this plugin.\n- If a tool fails, state the limitation briefly and suggest a new search. Do\n not fabricate partial inventory, prices, availability, or policies.\n"
"---\nname: pricewin-travel-search\ndescription: Search and compare live hotel and flight prices with the Pricewin MCP server, 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 an OpenTravel hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.\n---\n\n# Pricewin Travel Search\n\nUse only the Pricewin MCP dependency declared in `agents/openai.yaml`. Do not\nreplace it with browser automation, shell commands, direct API calls, or\ninvented booking URLs.\n\n## Collect the required trip details\n\nFor a hotel search, obtain:\n\n- destination or city;\n- check-in and check-out dates;\n- number of adults, defaulting to 2 when the user does not specify;\n- number of rooms, defaulting to 1.\n\nFor a flight search, obtain:\n\n- origin and destination airport IATA codes;\n- departure date and optional return date;\n- number of adults, defaulting to 1;\n- cabin, defaulting to economy.\n\nResolve unambiguous relative dates from the current date. Ask one concise\nfollow-up when a required date, destination, or airport is genuinely ambiguous.\nNever invent a date or silently choose among multiple plausible airports.\n\nPass `language` matching the user's language when supported. Do not put\nunrelated conversation or personal data in `queryText`.\n\n## Search hotels\n\n1. Call `search_hotels_live` with the destination, dates, occupancy, and only\n the filters the user actually requested.\n2. Read `sessionId` and `nights` from the response.\n3. Call `poll_search_results` with that `sessionId` and `nights`.\n4. If the response is pending or partial with no useful results, poll again\n until results arrive, the search completes or fails, or the session expires.\n5. Present a concise comparison of relevant results. Label the source and\n currency exactly as returned.\n\nUse `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied\nthat constraint. Do not claim that a result is the cheapest in the whole\nmarket; describe it as the cheapest among the sources returned for this search.\nA failed or missing source does not invalidate results from other sources.\n\n## Inspect an OpenTravel direct hotel\n\nCall `get_hotel_detail` only for a hotel identified as an OpenTravel direct\nlisting.\n\n- Prefer its `propertyId` from `opentravelResults`.\n- Reuse the user's dates and occupancy.\n- Use `hotelName` plus `city` only when the property is already known to be an\n OpenTravel direct listing and no `propertyId` is available.\n- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.\n\nPresent the returned photos, amenities, availability, room capacity, total\nprice, per-night price, and currency without changing their meaning. State\nclearly when availability or a price is missing.\n\n## Answer a question about a hotel\n\nFor questions about a hotel itself — check-in and check-out times, facilities,\nphotos, description, room types — call `get_hotel_info` with the `propertyId`\nof an OpenTravel direct listing, usually from `opentravelResults` of a search\nalready made. It needs no dates and returns no prices or availability; for\nthose, use `get_hotel_detail`. When the property has not published a field,\nsay so rather than filling it in.\n\n## Explain a cancellation policy\n\nCall `get_cancellation_policy` only after `get_hotel_detail` supplies both:\n\n- the property's `propertyId`; and\n- the selected room's `ratePlanId`.\n\nPass the check-in date so the tool can compute an exact deadline. Report the\nreturned non-refundable status, refund percentage, free-cancellation window,\ndeadline, and summary. Never infer a policy or deadline when the tool does not\nreturn one.\n\n## Search flights\n\n1. Call `search_flights_live` with IATA codes, departure date, optional return\n date, adults, and cabin.\n2. Read the returned `sessionId`.\n3. Use `poll_flight_results` when the host exposes it to the model; otherwise\n let the Pricewin flight widget perform its app-side polling.\n4. Continue only until useful results arrive, the search completes or fails, or\n the session expires.\n5. Present relevant options with source, carrier, times, stops, cabin, currency,\n and fare exactly as returned.\n\nKeep outbound and return legs distinct. Each leg is a separate one-way ticket\nwith its own booking link: when you pair an outbound and a return flight, give\nthe total as the sum of the two fares and say that each leg is booked\nseparately. Never present a pair as one round-trip ticket, and do not imply that\na fare is still available after the live result expires.\n\n## Request a booking at an OpenTravel direct hotel\n\nOnly an OpenTravel direct listing can be booked this way; an Agoda,\nBooking.com or Traveloka result cannot, and the user follows its own link\ninstead.\n\n1. Call `request_booking` with the `propertyId`, `roomTypeId`, dates and the\n guest's name, phone number and email. Ask for whichever of those three is\n missing; they go to the hotel, which needs them to honour the reservation.\n2. Relay the tool's reply as written. The two facts it leads with — that no\n room is held and that nothing has been charged — are the ones the guest\n acts on.\n3. Keep the `confirmationCode` it returns; `check_booking_status` reads the\n request's state back with it.\n\nThere is no payment step, now or later. Never ask how the guest wants to pay,\nand never mention a card, transfer, QR code, payment link or deposit — not\neven one the guest named earlier. The guest pays the property on arrival.\n\n## Cancel a booking\n\n1. Call `get_cancellation_policy` first, with the `propertyId`, `ratePlanId`\n and check-in date of the booked room, and tell the guest what they will get\n back — or that the property has published no policy.\n2. Call `request_cancel_token` with the confirmation code and the email on the\n booking. This cancels nothing; it emails a single-use token.\n3. Ask the guest to paste the token from that email. Never invent, guess or\n reuse one.\n4. Confirm the booking and the refund amount with the guest in their own\n language, get an explicit yes, then call `cancel_booking` with the code,\n the token and the guest's reason.\n\n`cancel_booking` cannot be undone. If there is no token yet, the answer is\nstep 2, never step 4.\n\n## Safety and output rules\n\n- Use only these eleven tools: `search_hotels_live`, `poll_search_results`,\n `search_flights_live`, `poll_flight_results`, `get_hotel_detail`,\n `get_hotel_info`, `get_cancellation_policy`, `request_booking`,\n `check_booking_status`, `request_cancel_token`, and `cancel_booking`.\n- Treat all prices as time-sensitive and avoid guarantees or unsupported\n \"lowest price\" claims.\n- Use only outbound URLs returned by the tools. Never construct, append,\n rewrite, or guess a booking URL.\n- Collect the guest's name, phone and email only to send a booking request,\n and only when the guest is actually sending one. Never ask for card data,\n bank details, credentials, or any other payment information: no tool here\n accepts them, and no step of this plugin takes money.\n- Do not modify an existing booking. There is no tool for it; a change means\n cancelling and sending a new request, and saying so plainly.\n- If a tool fails, state the limitation briefly and suggest a new search. Do\n not fabricate partial inventory, prices, availability, or policies.\n"
Full snapshot data
{
"description": "Search and compare live hotel and flight prices with the Pricewin MCP server, 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 an OpenTravel hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 599
}
],
"name": "pricewin-travel-search",
"skill_md_contents": "---\nname: pricewin-travel-search\ndescription: Search and compare live hotel and flight prices with the Pricewin MCP server, 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 an OpenTravel hotel or room, check a rate's cancellation policy, book a partner hotel, or cancel a booking they made this way.\n---\n\n# Pricewin Travel Search\n\nUse only the Pricewin MCP dependency declared in `agents/openai.yaml`. Do not\nreplace it with browser automation, shell commands, direct API calls, or\ninvented booking URLs.\n\n## Collect the required trip details\n\nFor a hotel search, obtain:\n\n- destination or city;\n- check-in and check-out dates;\n- number of adults, defaulting to 2 when the user does not specify;\n- number of rooms, defaulting to 1.\n\nFor a flight search, obtain:\n\n- origin and destination airport IATA codes;\n- departure date and optional return date;\n- number of adults, defaulting to 1;\n- cabin, defaulting to economy.\n\nResolve unambiguous relative dates from the current date. Ask one concise\nfollow-up when a required date, destination, or airport is genuinely ambiguous.\nNever invent a date or silently choose among multiple plausible airports.\n\nPass `language` matching the user's language when supported. Do not put\nunrelated conversation or personal data in `queryText`.\n\n## Search hotels\n\n1. Call `search_hotels_live` with the destination, dates, occupancy, and only\n the filters the user actually requested.\n2. Read `sessionId` and `nights` from the response.\n3. Call `poll_search_results` with that `sessionId` and `nights`.\n4. If the response is pending or partial with no useful results, poll again\n until results arrive, the search completes or fails, or the session expires.\n5. Present a concise comparison of relevant results. Label the source and\n currency exactly as returned.\n\nUse `hotelName`, `area`, `priceMin`, or `priceMax` only when the user supplied\nthat constraint. Do not claim that a result is the cheapest in the whole\nmarket; describe it as the cheapest among the sources returned for this search.\nA failed or missing source does not invalidate results from other sources.\n\n## Inspect an OpenTravel direct hotel\n\nCall `get_hotel_detail` only for a hotel identified as an OpenTravel direct\nlisting.\n\n- Prefer its `propertyId` from `opentravelResults`.\n- Reuse the user's dates and occupancy.\n- Use `hotelName` plus `city` only when the property is already known to be an\n OpenTravel direct listing and no `propertyId` is available.\n- Do not call this tool for an Agoda, Booking.com, or Traveloka-only result.\n\nPresent the returned photos, amenities, availability, room capacity, total\nprice, per-night price, and currency without changing their meaning. State\nclearly when availability or a price is missing.\n\n## Answer a question about a hotel\n\nFor questions about a hotel itself — check-in and check-out times, facilities,\nphotos, description, room types — call `get_hotel_info` with the `propertyId`\nof an OpenTravel direct listing, usually from `opentravelResults` of a search\nalready made. It needs no dates and returns no prices or availability; for\nthose, use `get_hotel_detail`. When the property has not published a field,\nsay so rather than filling it in.\n\n## Explain a cancellation policy\n\nCall `get_cancellation_policy` only after `get_hotel_detail` supplies both:\n\n- the property's `propertyId`; and\n- the selected room's `ratePlanId`.\n\nPass the check-in date so the tool can compute an exact deadline. Report the\nreturned non-refundable status, refund percentage, free-cancellation window,\ndeadline, and summary. Never infer a policy or deadline when the tool does not\nreturn one.\n\n## Search flights\n\n1. Call `search_flights_live` with IATA codes, departure date, optional return\n date, adults, and cabin.\n2. Read the returned `sessionId`.\n3. Use `poll_flight_results` when the host exposes it to the model; otherwise\n let the Pricewin flight widget perform its app-side polling.\n4. Continue only until useful results arrive, the search completes or fails, or\n the session expires.\n5. Present relevant options with source, carrier, times, stops, cabin, currency,\n and fare exactly as returned.\n\nKeep outbound and return legs distinct. Each leg is a separate one-way ticket\nwith its own booking link: when you pair an outbound and a return flight, give\nthe total as the sum of the two fares and say that each leg is booked\nseparately. Never present a pair as one round-trip ticket, and do not imply that\na fare is still available after the live result expires.\n\n## Request a booking at an OpenTravel direct hotel\n\nOnly an OpenTravel direct listing can be booked this way; an Agoda,\nBooking.com or Traveloka result cannot, and the user follows its own link\ninstead.\n\n1. Call `request_booking` with the `propertyId`, `roomTypeId`, dates and the\n guest's name, phone number and email. Ask for whichever of those three is\n missing; they go to the hotel, which needs them to honour the reservation.\n2. Relay the tool's reply as written. The two facts it leads with — that no\n room is held and that nothing has been charged — are the ones the guest\n acts on.\n3. Keep the `confirmationCode` it returns; `check_booking_status` reads the\n request's state back with it.\n\nThere is no payment step, now or later. Never ask how the guest wants to pay,\nand never mention a card, transfer, QR code, payment link or deposit — not\neven one the guest named earlier. The guest pays the property on arrival.\n\n## Cancel a booking\n\n1. Call `get_cancellation_policy` first, with the `propertyId`, `ratePlanId`\n and check-in date of the booked room, and tell the guest what they will get\n back — or that the property has published no policy.\n2. Call `request_cancel_token` with the confirmation code and the email on the\n booking. This cancels nothing; it emails a single-use token.\n3. Ask the guest to paste the token from that email. Never invent, guess or\n reuse one.\n4. Confirm the booking and the refund amount with the guest in their own\n language, get an explicit yes, then call `cancel_booking` with the code,\n the token and the guest's reason.\n\n`cancel_booking` cannot be undone. If there is no token yet, the answer is\nstep 2, never step 4.\n\n## Safety and output rules\n\n- Use only these eleven tools: `search_hotels_live`, `poll_search_results`,\n `search_flights_live`, `poll_flight_results`, `get_hotel_detail`,\n `get_hotel_info`, `get_cancellation_policy`, `request_booking`,\n `check_booking_status`, `request_cancel_token`, and `cancel_booking`.\n- Treat all prices as time-sensitive and avoid guarantees or unsupported\n \"lowest price\" claims.\n- Use only outbound URLs returned by the tools. Never construct, append,\n rewrite, or guess a booking URL.\n- Collect the guest's name, phone and email only to send a booking request,\n and only when the guest is actually sending one. Never ask for card data,\n bank details, credentials, or any other payment information: no tool here\n accepts them, and no step of this plugin takes money.\n- Do not modify an existing booking. There is no tool for it; a change means\n cancelling and sending a new request, and saying so plainly.\n- If a tool fails, state the limitation briefly and suggest a new search. Do\n not fabricate partial inventory, prices, availability, or policies.\n"
}SHA-256 of public snapshot: 3347a804522c4f87a995ea65652152ee8f5aa6b6232a459069c2ffe3f4b711fe