ALL Accor

# TOOL: get_hotel_offers ## Scope: tool description field — injected once, at tool registration. Retrieves room-level offers for a specific Accor hotel. ## WHEN TO USE Call this tool when the user wants to: - book a specific hotel or room type - view available room types and their rates - compare pricing options within a single hotel ## WHEN NOT TO USE You MUST NOT call this tool without a valid hotel ID obtained from a prior `search_best_hotel_rates` or `search_hotel_by_name` tool response. If the hotel was not present in a previous tool response, call `search_best_hotel_rates` or `search_hotel_by_name` first to obtain the ID. You MUST NOT invent, guess, or reuse a hotel ID from memory. ## CHAINING After this tool returns results, always generate a follow-up message using the FOLLOW-UP rendering rules for `get_hotel_offers`. You MUST NOT summarize room details in free prose before the widget renders. ## OUTPUT Renders a room carousel widget showing available room types, photos, descriptions, and base pricing.

get_hotel_offers

# TOOL: search_best_hotel_rates **Scope:** tool description field --- injected once, at tool registration. Retrieves best available rates for Accor hotels within a geographical area. ## WHEN TO USE Call this tool when the user is browsing or searching for hotels in an area --- for example: "hotels in Barcelona", "hotels near the Eiffel Tower", "find me a 4-star hotel in Lyon this weekend". Call this tool again whenever the user refines their search by changing: - destination or geographic area - check-in or check-out dates - number of guests (adults or children) - price range (min or max budget) - star rating - hotel brand - etc. ## WHEN NOT TO USE You **MUST NOT** call this tool when the user refers to a specific hotel by name (e.g. "I want to stay at the Raffles London", "show me the Mercure Opéra"). Use `search_hotel_by_name` instead. You **MUST NOT** invent or assume filter values. Only pass filters the user has explicitly stated. Never add default star ranges or price ranges unless the user requested them. You **MUST NOT** call this tool when a hotel is already selected in the widget context and the user's message refers to that same hotel without naming a different property. A hotel is selected when the text block pushed via `updateModelContext` carries a `current-hotel-id` other than `none`. In that case, answer directly from the already-available context and offers --- do not re-run the area search. ## CHAINING After this tool returns results, always generate a follow-up message using the FOLLOW-UP rendering rules for `search_best_hotel_rates`. You **MUST NOT** summarize results in free prose before the widget renders. ## OUTPUT Renders an interactive map and hotel list widget to the user.

search_best_hotel_rates

# TOOL: search_hotel_by_name ## Scope: tool description field — injected once, at tool registration. Resolves a hotel name to one or more Accor properties using fuzzy matching. Incomplete names, partial matches, and typos are supported. ## WHEN TO USE Call this tool when the user names a specific Accor hotel (for example an ibis, Novotel or Sofitel property), even partially or with a typo. Examples: - "Je veux réserver à l'ibis d'Issy" - "Book the Sofitel Lyon" - "What are the rates at the Pullman Paris Tour Eiffel?" - "Show me rooms at the Novotel near CDG" - "Is the Novotel Paris les Halles available tonight?" Use this tool instead of `search_best_hotel_rates` when the user already has a specific hotel in mind, not when they are browsing options in an area. ## WHEN NOT TO USE You MUST NOT call this tool when the user is browsing hotels in a general area without naming a specific property (e.g. "hotels in Barcelona", "hotels near the Eiffel Tower"). Use `search_best_hotel_rates` instead. ## OUTPUT AND CHAINING Returns one of three states: - **single_match** → call `get_hotel_offers` with hotel.id. Do NOT ask for confirmation. - **multiple_matches** → do NOT call `get_hotel_offers`. Wait for user selection. - **no_match** → do NOT call `get_hotel_offers`. Response formatting for each state is specified in the post-tool instructions. ## RULES - You MUST NOT display room or rate information from this tool's response. Room data is returned exclusively by `get_hotel_offers`. - You MUST NOT invent hotel IDs, prices, locations, or availability. - Hotel IDs passed to `get_hotel_offers` MUST come from this tool's response.

search_hotel_by_name

Starts the sign-in / sign-up flow for the user's ALL — Accor Live Limitless loyalty account (triggers the host's OAuth login). WHEN TO USE — Invoke this tool immediately, and without asking for confirmation, whenever the user explicitly asks to sign in, sign up, log in, or connect their ALL / Accor account. This includes when the user clicks the widget's "Sign in / Sign up" button (which posts a sign-in request on their behalf) or says things like "sign me in", "log in", or "connect my account". In these cases call this tool directly — do not reply with text or ask a follow-up question instead of calling it. WHEN NOT TO USE — Do not invoke it proactively, to check whether the user is already signed in, or in response to any message that is not an explicit sign-in request.

sign_in