create_trip
ChatGPTcreate_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.
edit_trip
ChatGPTedit_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.
plan_trip
ChatGPTplan_trip is Travel Vibes' trip-planning tool: whenever the user asks to plan, create, build, or organize a trip or itinerary, plan_trip can create the trip in a well-organized travel scratchpad widget, so the user conveniently has the whole trip plan at a glance while planning in the chat. Using plan_trip presents the trip to the user in a more organized form than a prose itinerary returned in chat. 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…", etc., 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"). A call needs only what the user gave: unspecified details (dates, length, vibe, budget) are filled with sensible defaults, and the first version is a complete, polished itinerary produced in a single call. Dates, vibe and budget are not inputs of this tool at all: itinerary_html is its only field; the defaults cover them and the user adjusts them afterwards. A conversation holds one trip: a later plan_trip call in it revises that trip rather than creating a second one. Its itinerary_html replaces the whole document, so it carries the current itinerary with only the requested change applied and everything else as it was; a document that holds only the changed part would replace the trip with that part. The itinerary is not generated by the Travel Vibes backend: the itinerary_html a call carries is the trip, composed as TipTap-compatible HTML and rendered by the widget exactly as given. === itinerary_html === itinerary_html is one self-contained HTML document (compact HTML, not markdown). Supported tags: h1, h2, h3, p, strong, em, ul, ol, li, table, colgroup, col, tbody, tr, th, td, br, span. Inline style is supported only for status colors and colored text through the CSS variables below. Not supported, and dropped if present: <img> or photos, map blocks (<div data-node-type="mapBlock">), data-entity-id attributes, <script>, <style>, class attributes, and TipTap artifacts (data-id, default colspan/rowspan). Photos and maps are added later inside the app. Styling the renderer preserves (anything else is discarded): - The title and the date/route line are centered: style="text-align: center;" on those <h1>/<p>. - Which rows to highlight is the model's call; for the reader's convenience it is worth marking booked items green and unbooked ones red: background-color: var(--tt-color-highlight-green) or var(--tt-color-highlight-red) on the <td> (the editor keeps colour on cells, not on rows). - Every table cell's content sits inside <p>…</p> (e.g. <th><p>Dates</p></th>, <td><p>Apr 10</p></td>). - Tickable checklist (the PACKING LIST): <ul data-type="taskList"><li data-checked="false" data-type="taskItem"><label><input type="checkbox"><span></span></label><div><p>Item text</p></div></li></ul> Structure, in this order: 1. <h1> trip title </h1> 2. <p> date range | duration | route </p> 3. Logistics, the relevant ones only: <h1>FLIGHT INFO</h1> / <h1>ACCOMMODATION</h1> / <h1>BOOKING CHECKLIST</h1>, each a <table> with a header row (<th>) and data rows (<td>); a placeholder "…" row where the user gave no data; highlighted cells as under Styling. 4. <h1>ACTIVITY PLAN</h1>, then for each day: - <h2>Day N | Weekday, Month Dth — Area</h2> - <p><strong>Location:</strong> …</p> and <p><strong>Accommodation:</strong> …</p> - a <table> with the header Time | Activity/Location | Duration | Notes, one row per activity (real, specific place names, with a "⭐ 4.x" rating inline where known) - <p><strong>Day N Food Options:</strong></p> then a <ul><li> list of real restaurants, cafes and bars The labels (Location, Accommodation, Day N Food Options) and the table headers are in the itinerary's language. 5…
show_trip
ChatGPTshow_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.