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, or the exact current-Home memberRef needed for an ordinary assignment. assignableMembers includes only authorized adults and children with an opaque assignment reference; never ask the customer to supply or guess it. This tool excludes vehicle records, birthdates, exact ages, allergies, medications, health conditions, custody details, private notes, credentials, payment data, 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 planning help based on enabled meal slots, ordinary family schedules and non-medical preferences, FamilyWise events, or calendar busy times each connection owner explicitly allowed for assistant context. It returns opaque memberRef values for ordinary adult or child assignments and excludes birthdates, exact ages, allergies, dietary or 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, desserts, snacks, beverages, recipes, grocery lists, or household list items in their FamilyWise Home. Food results use one canonical foodCategory, structured ingredient items, separate mealSlots, and category-appropriate pairings or add-ons. Use the returned record and list IDs for any follow-up write.

familywise_get_saved_content

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 only a current assignableMembers memberRef for an assignee, use the current record version for updates, preview the exact change, and require confirmation.

familywise_save_household_task

Use this when the user asks to create or update one FamilyWise reminder. First read household operations and use only current assignableMembers memberRef values for assignees. This updates the shared reminder; each phone manages its own notification delivery. Preview the exact change and require confirmation.

familywise_save_reminder

Use this when the user asks to create or update one routine item. First call familywise_get_household_operations for the selected Home, use the exact section and only memberRef values returned in assignableMembers, preserve unrequested fields, and never ask the customer for an internal ID or substitute a name or meal-planning ID. Preview the exact assignment and require confirmation.

familywise_save_routine_item

Use this when the user asks to create or update one routine section. First call familywise_get_household_operations for the selected Home and use only exact memberRef values returned in assignableMembers; never ask the customer for an internal ID or substitute a name or meal-planning ID. The seven day flags run Sunday through Saturday. Preview the exact assignment and require confirmation.

familywise_save_routine_section

Use this when the user explicitly asks to save one categorized meal, side, dessert, snack, beverage, other food, or recipe to their FamilyWise Home. Ingredients must be separate bounded items; mealSlots are only for main meals; pairings and add-ons must match the category. FamilyWise does not fetch source URLs or ingest arbitrary image URLs. First check duplicates, preview 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, use only current memberRef values for any adult or child assignees, 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 saved FamilyWise meal, side, dessert, snack, beverage, other food, or recipe. First read the saved record, preserve its canonical category, structured ingredients, meal slots, pairings, and add-ons unless explicitly changed, preview every change, pass its current version, and require confirmation.

familywise_update_food

Use this when the user explicitly asks to change non-medical shared Home planning defaults such as enabled meal rows, planning days, 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. Allergy, dietary-health, medication, custody, and private member details are not supported here and must stay in FamilyWise HQ.

familywise_update_planning_preferences