Grocer

Use this when the user asks to add one item to an existing Grocer list. If the user hasn't said which list to use, and hasn't picked one earlier in this chat, don't choose for them: find their lists with list_grocery_lists, then ask which one to add to or whether to create a new list. Generate a fresh UUID for item_id and reuse it only if retrying this exact addition. Put the amount in quantity ("2", "1 lb") rather than the title. If the list already has an item with the same name, ignoring case, plurals and amounts in the name, it is merged into that line instead of added twice: amounts in the same unit are added up ("2" + "1" is "3", "2 lb" + "1 lb" is "3 lb"), other amounts are kept side by side ("2 cups + 200 g"), and a line that was checked off is unchecked and given the new amount. The result's merge says what happened, and item is then the line it merged into, whose id differs from item_id. When the item is for a recipe or meal, set source to its name. Set category to the item's aisle. Viewers cannot add items.

add_item

Use this when the user asks to add more than one item to an existing Grocer list, such as the ingredients for a recipe or a week of meals. If the user hasn't said which list to use, and hasn't picked one earlier in this chat, don't choose for them: find their lists with list_grocery_lists, then ask which one to add to or whether to create a new list. Prefer it over repeated add_item calls. Scale each ingredient's amount to the servings the user asked for, and put it in quantity ("2", "1 lb", "3 cups") rather than the title. Leave out pantry staples most kitchens already have (salt, pepper, cooking oil, spices, flour, sugar) unless the user said they need them; ask first, or list them separately for the user to pick. Set each item's source to the recipe or meal it is for, so the user can tell recipes apart on the list, and its category to its aisle. Adds up to 100 items in one call, in the given order, after the list's current items; all are added or none are. If the list already has an item with the same name, ignoring case, plurals and amounts in the name, it is merged into that line instead of added twice: amounts in the same unit are added up ("2" + "1" is "3", "2 lb" + "1 lb" is "3 lb"), other amounts are kept side by side ("2 cups + 200 g"), and a line that was checked off is unchecked and given the new amount. An item that matches another in the same call is merged the same way. Each result's merge says what happened, and its item is the line it landed on; tell the user which items were merged. Generate a fresh UUID for each item_id and reuse the same IDs only if retrying this exact addition; a retry never adds an amount twice. Viewers cannot add items.

add_items

Use this when the user wants to share a Grocer list with someone they already share with, as returned by list_grocery_collaborators. Adds them to the list right away, with no invite link; they see it in their Grocer app. Only the list's owner can do this. An editor can add, edit and check off items; a viewer can only read. Use editor unless the user asks for read-only access. For anyone not returned by list_grocery_collaborators, use share_grocery_list.

add_grocery_list_collaborator

Use this when the user asks to check off or uncheck a specific item in a Grocer list. Viewers cannot change items.

set_item_completed

Use this when the user checks off or unchecks more than one item in a Grocer list at once, such as "I bought everything in produce" or "got the milk, eggs and bread". Prefer it over repeated set_item_completed calls. First read the list with get_grocery_list and choose the matching item IDs; for a category, use an item's manual_category when it is set and otherwise judge by its title. Changes up to 100 items in one call; all are changed or none are. Viewers cannot change items.

set_items_completed

Use when the user asks to create a named category and move a specific item into it. Grocer currently saves custom categories on items, so an item is required and empty categories cannot be created. Identify the exact list and item first. Viewers cannot create categories.

create_category

Use this when the user asks to create a new Grocer list, including when they choose a new list for items they asked to add. Generate a fresh UUID for list_id and reuse it only if retrying this exact creation.

create_list

Soft-delete one item after confirming its exact name and list with the user. Get the item with get_grocery_list first. Pass confirmation exactly as DELETE <item title> FROM <list title>, using the current titles returned by Grocer. Viewers cannot delete items.

delete_item

Soft-delete an entire list and hide it from all members. Only its owner may do this. Confirm the exact list title with the user, then pass confirmation exactly as DELETE <list title>, using the current title returned by Grocer.

delete_list

Change the name, quantity, or notes of one existing item. Identify the exact list and item first. Supply only fields the user asked to change, and confirm with the user before clearing or replacing existing notes. The result's previous object holds each replaced value, so an edit can be undone with another edit_item call. Viewers cannot edit items.

edit_item