HOTELS Trip & Travel Stays

create_trip shows the trip to the user in the Travel Vibes Scratchpad widget: the first call in a conversation creates the trip from the complete itinerary written in the format plan_trip returned. A conversation holds one trip. A later change to that trip is edit_trip's job (named sections and text replacements, nothing resent); a later create_trip call in the same conversation replaces the whole document with the itinerary it carries. `itinerary_html` is the tool's only field: the complete itinerary in the format plan_trip returned.

create_trip

edit_trip changes the trip this conversation holds in the Travel Vibes Scratchpad widget by sending only the changed part. `sections` carries, per entry, a section's heading as it stands in the itinerary (the trip title, FLIGHTS, ACCOMMODATION, BOOKINGS, a day's heading such as "Day 3 | Saturday, April 12th — Asakusa", or the same headings in the itinerary's language) and that section's complete new content in the itinerary format, opening with that heading; every section not named stays as it is. Each entry replaces its whole section, so it carries every item the user did not ask to remove; an item left out is removed from the trip. A missing FLIGHTS, ACCOMMODATION or BOOKINGS section, or the day after the last, is named by its own heading and lands in its place; any other new section rides in the content of the section it follows. `replace` carries, per entry, text as it stands in the itinerary and its replacement, applied wherever it occurs (a hotel name used in several sections). A call carries one or both. The result lists each entry as applied or not, with the reason, and carries the complete itinerary after the call, the current state for any later edit.

edit_trip

plan_trip is the first step of planning a trip with Travel Vibes: whenever the user asks to plan, create, build, or organize a trip or itinerary, plan_trip returns the itinerary format the Travel Vibes Scratchpad widget displays (the structure and a worked example). An itinerary written in that format is what create_trip shows to the user. The tool is useful whenever the user wants a trip or itinerary for a destination: when users ask about travel in a form like "plan…", "trip to…", "X days in…", "weekend in…", "I'm travelling to…", "I'm going to…", or even a brief pairing of the destination with trip attributes (duration, dates, who's going, interests, vibe). "Plan a trip to Tokyo" is a request where using the tool is already useful, so is "I want a food-first long weekend in Mexico City", and so are similar requests in another language ("Planea un viaje a Roma de 4 días").

plan_trip

show_trip shows the user's existing trip in the Travel Vibes Scratchpad widget again, exactly as it stands now: it reads the trip and changes nothing. It answers a request to see the trip again, reopen it, show it here again or refresh it, such as "Show my trip here again." Creating a trip is create_trip's job and changing one is edit_trip's. `trip_id` is the tool's only field, optional: the tripId an earlier create_trip or edit_trip result in this conversation carries; without it, the conversation's trip is shown.

show_trip