Bonder

Add one item to a trip's itinerary. type: transportation, accommodation, activity, or dining. Items are created as 'proposed' — a suggestion for the group to review — unless you pass status 'confirmed'. Only pass 'confirmed' when the user says the item is actually booked, and you must then also pass confirmation {sourceType, confirmationRef} (e.g. sourceType 'airline email', confirmationRef 'ABC123'); 'confirmed' without confirmation is rejected. Scheduling: on a dated trip pass either dayNumber (1 = the trip's first day; places the item on that date without a specific time) or an explicit startTime (ISO 8601 datetime) with the destination's IANA timezone — not both. endTime is optional and requires startTime. On an idea trip (no dates yet), only dayNumber is valid (an idea trip still has to be unlocked). Omit both to leave the item unscheduled. dayNumber must fit the trip's length — check get_trip first. location is looked up on Google Maps in the background, so name the place and its city ('Woodstock Brewhouse, Woodstock, VA') rather than giving a bare street address — an address on its own matches the building, which has no photo. For flights, supply transportMode flight and every known airline, number, exact schedule, and clear route in this same write. Read get_trip for destination IDs; do not assume the first flight is outbound or invent missing details. Ask when route direction is ambiguous. Requires an unlocked trip where you're the organizer or a co-planner (not a viewer).

add_to_itinerary

Check a trip's itinerary for gaps: nights with no place to stay, missing transport between destinations or to/from home, and days with nothing planned. Also checks whether the plan is realistic against the trip's preferences (too much time in transit, a drive over someone's limit, too many stops, stays too short), lists transport legs that need re-routing because the destinations changed, and flags items whose times overlap or end before they start, and transport legs out of order. Also lists stays and tickets still to book: nights or legs with only proposed options in the next 30 days, and confirmed ones with no booking reference saved. Leaves out anything the user marked "Not needed" or snoozed on their Bonder to-do list. These are the same checks the Bonder app shows. Use it when the user asks what's missing, what's left to book, whether the plan is complete or realistic, or what to sort out next. A gap means it's missing from Bonder, not necessarily from the real trip, and a feasibility warning is advice, not a rule — so report findings as questions and suggest fixes, never change the trip without the user's go-ahead. Each gap gives the dayNumber (and, for transport, the route) that add_to_itinerary takes. Use the trip id from list_trips.

audit_trip

Permanently delete one expense and its split. Confirm with the user before calling this: name the expense and amount and say it can't be undone. Get expenseId from list_expenses. Not the way to correct an expense; use update_expense for that. You can delete an expense you logged, one you're in the split of, or any expense if you have trip-wide expense access, on an unlocked trip where you're the organizer or a co-planner.

delete_expense

Get one trip's details, accepted participants, and ordered destination route context. Read this before linking a flight; resolve outbound, return, or adjacent interior direction from the user's journey. Ask if direction or a connection is ambiguous.

get_trip

Get a trip's itinerary items grouped by day, in order. Items may be 'proposed' (suggested, not yet agreed) or 'confirmed' (the group locked it in). Each line ends with the item's id — pass that to update_itinerary_item or remove_itinerary_item to change or delete it. Day headings use the same dayNumber those tools take (1 = the trip's first day). Times are already local: each is the wall-clock date and time in the named IANA zone, with its UTC offset shown for reference — read them as-is, don't convert them again. Use the trip id from list_trips.

get_itinerary

List a trip's expenses that you can see, newest first: amount and currency, date, category, who paid (when recorded), who logged it, payment status, split, and privacy. Private expenses only appear when you logged them, are in their split, or have trip-wide expense access, the same as in the app. Also lists the people (with ids) you can name in a split. Requires an unlocked trip. Each line ends with the expense id for update_expense and delete_expense.

list_expenses

List every trip the connected Bonder user participates in (owned or invited), with dates, status, and role. Status is the trip's state: only an unlocked trip can be planned (idea trips included), and a historical record can't be until it's converted in the app. Your role decides the rest: a Viewer can't change anything. Start here to find a trip id for the other tools.

list_trips

Log one expense on a trip, optionally split between people. amount is the total in currency (a 3-letter ISO code; defaults to the currency of the trip's latest expense, otherwise USD). date is required: the day the money was spent, in the user's local calendar, as YYYY-MM-DD. category: accommodation, transportation, food_dining, activities, shopping or other (default other). paidBy is the userId of whoever paid, if known. split: {type: 'none' | 'even' | 'percentage' | 'amount', everyone?, participants?}. For an even split among every accepted participant pass {type: 'even', everyone: true}; otherwise list participants by userId (from get_trip or list_expenses) or guestId (expense contacts, from list_expenses). Even splits compute the shares for you; percentage splits need a percentage per participant totalling 100; amount splits need an amount per participant adding up to the expense total. Expenses are private by default (visible to you, people in the split, and anyone you've shared expenses with); pass isPrivate: false to show it to the whole trip. Use the exact amount from a receipt or the user's words; don't estimate. Requires an unlocked trip where you're the organizer or a co-planner (not a viewer).

add_expense

Permanently delete one itinerary item. Confirm with the user before calling this — name the item and say it can't be undone. Get itemId from get_itinerary (each line ends with its id). This cannot be undone, and it is not the way to reschedule or rename something — use update_itinerary_item for that. Refused when the item has votes or feed discussion attached, since deleting it would throw away the group's input; those have to be removed in the app. Requires an unlocked trip where you're the organizer or a co-planner (not a viewer).

remove_itinerary_item

Save a research finding to the trip's Notebook. Use this for trip-level facts and logistics — visa/document requirements, driving rules, packing, local customs, budget notes, health & safety — or to save a useful link. Not for schedulable events (use add_to_itinerary for those). Provide body for a note, or url to save a link instead (one or the other). topic must be one of: driving, documents_visas, packing, local_customs, budget, health_safety, general. Optionally set impliedAction (a short next step, e.g. 'Get an International Driving Permit') and scope the finding to one day (dayNumber, 1 = the trip's first day) or one itinerary item (itineraryItemId) — never both. Saved items show a 'From assistant' badge in the app. Requires an unlocked trip where you're the organizer or a co-planner (not a viewer).

save_trip_research