FamilyWise HQ

Use this when the user explicitly asks to delete an existing shared FamilyWise list and its items. First read saved content, name the list and explain that its items will also leave the shared Home, pass the current version, and require confirmation.

familywise_delete_list

Use this when the user explicitly asks to remove one existing FamilyWise list item. First read saved content, name the item and list, pass the current item version, and require confirmation.

familywise_delete_list_item

Use this when the user explicitly asks to remove one existing FamilyWise meal, side, snack, dessert, or recipe. First read the record, name it, explain that it will leave the shared library, pass its current version, and require confirmation.

familywise_delete_food

Use this when the user needs household tasks, task history, routines, reminders, vehicles, or maintenance records from the shared Home before advice or a proposed change. It excludes medications, health conditions, custody details, private notes, device notification IDs, and external provider data.

familywise_get_household_operations

Use this when the user wants to read up to 31 days from their FamilyWise Home. Call it before proposing or applying a meal-plan change so the exact Home and current day version are known.

familywise_get_meal_plan

Use this when the user wants meal suggestions that account for enabled meal slots, family eating schedules, food avoidances and preferences, FamilyWise events, or calendar busy times each connection owner explicitly allowed for assistant context. It excludes birthdates, health conditions, medications, custody details, private notes, raw provider events, external account details, and calendars that were not opted in.

familywise_get_planning_context

Use this when the user wants to find saved meals, sides, snacks, desserts, recipes, grocery lists, or household list items in their FamilyWise Home. Use the returned record and list IDs for any follow-up write.

familywise_get_saved_content

Use this when the user asks to create or correct one vehicle maintenance record. First read household operations, match the exact vehicle ID, include the next due date or mileage when known, and require confirmation.

familywise_log_vehicle_service

Use this when the user explicitly asks to rename an existing shared FamilyWise list. First read saved content, state the old and new title, pass the current list version, and require confirmation.

familywise_update_list

Use this when the user asks to create or update one household task. First read household operations, preserve unrequested fields, use the current version for updates, and require confirmation.

familywise_save_household_task

Use this when the user asks to create or update one FamilyWise reminder. First read household operations. This updates the shared reminder; each phone manages its own notification delivery. Require confirmation.

familywise_save_reminder

Use this when the user asks to create or update one routine item. First read household operations, use exact section and shared family-member IDs, preserve unrequested fields, and require confirmation.

familywise_save_routine_item

Use this when the user asks to create or update one routine section. First read household operations and the shared family roster. The seven day flags run Sunday through Saturday. Require confirmation.

familywise_save_routine_section

Use this when the user asks to create or update one household vehicle. First read household operations, preserve unrequested fields, and require confirmation.

familywise_save_vehicle

Use this when the user explicitly asks to save one meal, side, snack, dessert, or recipe to their FamilyWise Home. For a recipe found elsewhere, pass the structured recipe details and original source URL; FamilyWise does not fetch the page. First check duplicates, summarize the exact fields, and require confirmation.

familywise_save_food

Use this when the user explicitly asks to change the planned sides for breakfast, lunch, or dinner, or the planned dessert on one FamilyWise date. First read the meal plan, state the complete replacement set for that date, pass its current version, and require confirmation.

familywise_set_meal_components

Use this when the user has explicitly confirmed one exact FamilyWise breakfast, lunch, or dinner change. First call familywise_get_meal_plan, state the date and old and new values, then pass the returned version and a unique idempotency key.

familywise_set_meal_slot

Use this when the user explicitly asks to edit one FamilyWise-created event. First read planning context, state every changed field, pass the current event version, and require confirmation. This does not modify an external provider calendar event.

familywise_update_event

Use this when the user explicitly asks to rename, recategorize, complete, or reopen one existing FamilyWise list item. First read saved content, state the exact change, pass the current item version, and require confirmation.

familywise_update_list_item

Use this when the user explicitly asks to edit one existing FamilyWise meal, side, snack, dessert, or recipe. First read the saved record, state the exact fields that will change, pass its current version, and require confirmation; omitted fields are preserved.

familywise_update_food

Use this when the user explicitly asks to change shared Home planning defaults such as enabled meal rows, planning days, dietary rules, budget awareness, easy-meal behavior, late-meal timing, or side tracking. First read planning context, state every changed field, pass the current profile version, and require confirmation. This does not change private member health or custody details.

familywise_update_planning_preferences