lesgooo

For a user-requested plan opening, read get_checklist and get_expenses too. Reply in the user's conversational language, 25–60 words total, at most four short bullets plus ONE contextual question about ONE action, not a menu. Summarize dates (actual counts/ties, not an agreed date), places, open tasks and balances; omit empty modules and completed-task lists. Reading requires no identity; never guess personal debts. After a write, briefly report that result and one next-step question instead of repeating the overview. Respect requests for no suggestions. Read the saved plan explicitly requested by the user. If the user's link is a bare /when, /where, /rsvp, /checklist or /splitwise URL, do NOT call this tool: explain it is a local draft and ask for its saved share link, even when a different plan was used earlier. Never replace a supplied link with the previous plan. Returns today's date in time_zone (UTC by default), title, event details, participants and their availability/RSVP, best dates, place votes and currency. Pass since (an earlier server_time) to also read changes.

get_plan

Read the plan's shared costs (Splitwise tab): expenses, each person's balance, and the suggested payments to settle up. Amounts are in the plan's currency.

get_expenses

Read the plan's shared checklist: open and done items, with item_id.

get_checklist

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Record that the person you act for paid someone back (settling up). amount defaults to what they owe that person according to get_expenses. Only after the money was actually sent. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

record_payment

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Delete an expense, payment, checklist item or place that the person you act for added (e.g. to fix a wrong amount: remove, then add again). Entries added by others can't be removed here. Requires an explicit request to delete this specific entry. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

remove_entry

App-only transport for explicit interactions with shared web components. Reuses the web write gateway, validation and budgets. Requires the selected participant token for saved-plan edits.

widget_write

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Add, remove or replace one participant's available calendar dates (YYYY-MM-DD, today up to two years ahead). Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

set_availability

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Suggest a place the group can vote on (Where tab). Default source=auto searches the same Google Places autocomplete as the web and returns needs_selection with up to five candidates, without a write. A selected google_place_id loads official details and stores the Google Maps link, coordinates and metadata. Zero results use the supplied link or manual name/address. source=manual explicitly saves a link/manual location without lookup. Google lookup failure does not save a fallback automatically. Supplied Google Maps URLs remain available as a zero-results or explicit manual fallback; they do not bypass the default Google lookup. Duplicates are merged. Acts as the participant. Current stored state is available through get_plan. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

add_place

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Mark a checklist item done (done: true) or open again (done: false), by item_id from get_checklist. Current stored state is available through get_checklist. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

check_item

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Change the shared event everyone sees on the RSVP page: title, date/time, place or description. Covers group-agreed details or the user's title for their just-created plan. Uses the existing plan and participant credentials; omitted fields are unchanged, and an empty string clears a field. Times are local (no time zone); an omitted start_time means all-day when a start_date is provided. Availability alone does not specify an agreed event date. Current stored state is available through get_plan. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

update_event

Keep the final reply in the user's conversational language, 2–4 short sentences (25–60 words): report the verified result and ask ONE relevant optional next-step question about ONE action, not a choice menu. Mandatory missing details take priority. Suggestions never perform actions automatically; respect requests for no suggestions. Saved links let friends join without accounts. If CURRENT received UI context or actual host evidence confirms the same saved plan and last-action module are already open, do not call open_planner again; realtime updates the existing view. Historic context is insufficient. Otherwise open the last-action module with the selected credentials, or honor an explicit opening request. Up-vote ("up"), down-vote ("down") or remove your vote ("clear") on a place, by place_id from get_plan. Changes only the participant bound to the supplied credentials. Current stored state is available through get_plan. Service use restrictions: plan creation, participation and edits for users known to be under 13 (or a higher local minimum) are prohibited, including under a nickname. Personal data about known underage children, sensitive medical records, intimate content, card details, government IDs, passwords and verification codes are prohibited planning input. This tool covers ordinary non-sensitive group planning only.

vote_place

After completing and verifying the requested actions, keep the last requested action's module: availability=when, places/votes=where, RSVP/event details=rsvp, checklist=checklist, expenses/payments=splitwise. If CURRENT received user_planner_selection or actual host evidence confirms that SAME saved plan AND module are already open, DO NOT call open_planner again: saved changes appear through realtime subscriptions in the existing view, and opening again can create a duplicate tab/card. Report the verified result in chat. Historic UI context alone does not prove a view is still open. Call open_planner only when no matching current view is confirmed, the target plan/module differs, or the user explicitly requests another opening. When opening, pass the already selected participant_id and participant_token; never join again or guess identity merely for display. Verification reads, participant selection and completing missing new-plan name/title do not change the last requested action's module. For a user-requested plan opening, read get_checklist and get_expenses too. Reply in the user's conversational language, 25–60 words total, at most four short bullets plus ONE contextual question about ONE action, not a menu. Summarize dates (actual counts/ties, not an agreed date), places, open tasks and balances; omit empty modules and completed-task lists. Reading requires no identity; never guess personal debts. After a write, briefly report that result and one next-step question instead of repeating the overview. Respect requests for no suggestions. Open the interactive lesgooo planner. Optionally choose a saved plan link, module and previously selected participant credentials. Credentials preserve that person in the displayed view without another identity picker. Without a plan, show the same local draft as the web application; never save a shared plan automatically.

open_planner

Read the plugin settings layout. There are no account settings; the action opens device-local preferences.

No primitive account settings are available. An empty update is a no-op; device preferences are changed in the widget.