Michi - Travel App

Apply exactly one previously generated proposal after the user explicitly confirms it. Never call this in the same turn that created the proposal.

apply_proposal

Read a trip's days, saved places, categories, activities, and route legs for planning. Use list_trips first when the trip ID is unknown. The `categories` list is the complete set of category ids that can be assigned to places — new categories can only be created by trip members in the Michi app.

get_trip

List trips that the signed-in Google account can access, including its role in each trip.

list_trips

Prepare, but do not apply, a new order for every activity on one day. Pass the complete sequence of activity IDs, first to last — this is how you reshape a day: start at the hotel, group nearby stops, put timed visits where they belong. Call get_day_details first to see the current order, computed times, and travel between stops. Michi rebuilds the routes between activities automatically to match the new order. Activities you leave out keep their relative order and go last. Apply any pending content edits (propose_update_activity or propose_update_activities) for this day's activities before reordering — once a reorder is applied, an edit proposal prepared earlier for the same day's activities will fail to apply and will need to be recreated.

propose_reorder_day

Prepare, but do not apply, several activities at once (optionally across multiple days). Each item uses an existing placeId or a full place search result. Returns a single proposal the user approves once; on apply, all activities, any new places, and the routes between them are created together. Call get_trip first and set each new place's `categoryId` to the best-fitting existing category.

propose_activities

Prepare, but do not apply, an activity proposal. Use either an existing placeId or a complete place search result; the latter will also be saved to Places. Call get_trip first and set the new place's `categoryId` to the best-fitting existing category.

propose_add_activity

Prepare, but do not apply, a change to an existing place's category — set it to one of this trip's existing categories, or pass categoryId: null to clear it. Call get_trip first to see the trip's category list. This is the only way to change or remove a place's category; a new category cannot be created here.

propose_set_place_category

Prepare, but do not apply, a route-mode, departure-time, or manual-duration change between two activities. Prefer propose_set_route, which addresses a hop by its two activities.

propose_update_route

Prepare, but do not apply, the travel details for the hop between two activities that sit next to each other on a day — the transport mode, and optionally when you leave and how long it takes. Works whether or not that hop already has a route: Michi creates one automatically between consecutive activities. Call get_day_details first to see the day's order. To change which activities are next to each other, use propose_move_activity or propose_reorder_day instead.

propose_set_route

Prepare, but do not apply, a move of one activity — to a different spot in its day, or to another day. Call get_day_details first to see the current order. Michi rebuilds the routes around it automatically. To resequence a whole day at once, use propose_reorder_day. Apply any pending content edits (propose_update_activity or propose_update_activities) for this day's activities before moving one — once a move is applied, an edit proposal prepared earlier for the same day's activities will fail to apply and will need to be recreated.

propose_move_activity