Tools (2)

Extracted live via the executor SDK.

• search_hotels

  Use this tool ONLY when the user explicitly asks for HOTELS. The user's message must contain the word 'hotel' or 'hotels'. If the user asks for an Airbnb, apartment, hostel, or vacation rental, do NOT use this tool — it only has hotels.

  When to use

  • User explicitly mentions 'hotel' or 'hotels' (e.g., 'Find hotels in Paris', 'Show me hotels near the Eiffel Tower').
  • User requests hotels by style or type (e.g., 'boutique hotels in Rome', 'luxury eco-friendly hotels').

  When NOT to use — DO NOT TRIGGER for:

  • Airbnb, apartments, hostels, vacation rentals, or any non-hotel lodging — even if the user mentions a city. 'Find an Airbnb in Barcelona' is NOT a hotel request.
  • Restaurants, cafés, bars, or dining recommendations (e.g., 'best restaurants near the Eiffel Tower').
  • Flights, transportation, car rentals, or travel logistics.
  • Tourist attractions, activities, sightseeing, or things to do.
  • General city guides, weather, or travel tips.
  • Details about a specific hotel the user already knows — use get_hotel_details instead.
  • Multi-city comparisons in one query — run one search per city.

  How to use

  1. Start broad: set q to the city name (e.g., q='Paris'). Add filters only if the user specifies them.
  2. If a search returns 0 results, relax filters progressively — remove neighborhoods first, then widen price_levels, then remove styles.
  3. The q parameter matches each word independently, so 'boutique Paris' finds Paris hotels with 'boutique' in their description.
  4. Do NOT repeat terms in q that are already covered by neighborhoods or styles filters.

  Parameter guidance

  • q: Primary location keyword. Use ONE city or country name. Keep simple.
  • min_rating: Only set when user explicitly asks for quality (nice ≈ 4.2, great ≈ 4.5, excellent ≈ 4.7). Omit otherwise.
  • price_levels: Map budget hints to $/$$/$$$/$$$$. Note: $ hotels are rare — if 0 results, retry with $$ included.
  • neighborhoods: Use TripAdvisor format (e.g., '1st Arr. - Louvre', 'Le Marais'). Partial names work. If unsure, omit.
  • styles: Available values include Boutique, Mid-range, Luxury, Budget, Trendy, Romantic, Business, Family, Charming, Great View, Quaint, Historic, Classic.
  • travel_type: Infer from context — leisure for vacation, business for work trips, travel_manager for group bookings.
  • limit: Use 3–5 for quick picks, 10–20 for browsing.
  • offset: For pagination. To see the next page, set offset to the previous offset + limit (e.g., first call offset=0, second call offset=10).

  Policy

  • All results are Valpas-verified hotels only.
  • This tool is search-only — it does not book or reserve rooms. $$
• get_hotel_details

  Use this tool when the user wants to see full details about a specific hotel — including photos, amenities, reviews, rating breakdown, and booking links.

  When to use

  • User asks about a specific hotel by name (e.g., 'Tell me about Hotel Le Marais').
  • User clicks on or asks about a specific hotel from search results.
  • User wants to see photos, amenities, reviews, or booking options for a hotel.
  • User asks to compare two specific hotels — call this once per hotel.

  When NOT to use

  • User wants to browse or search for hotels — use search_hotels instead.

  How to use

  • Pass either the hotel's id from search results, or the hotel's name if the user mentions it directly.
  • If you have an id from a previous search, prefer using id for an exact match.
  • The response includes: name, address, rating, price level, photos, amenities, review count, rating breakdown, trip types, booking URL, and website URL.

  Policy

  • Read-only — does not book or modify anything.
  • Always provide the booking URL and website URL so the user can take action.