add_items_to_list
ChatGPTUse to add one or many groceries at once (send all items in a single call). Items are categorised automatically; an item that is already on the list is merged instead of duplicated. Give quantity and unit when known, or put the amount in the name (e.g. "500 g chicken breast").
add_recipe_ingredients_to_list
ChatGPTUse to put a saved recipe's ingredients on a shopping list. Quantities are scaled to the servings, compared with what is already on the list, and only the missing amounts are added; repeating the call does not duplicate. Set dry_run=true to preview first.
add_recipe_to_meal_plan
ChatGPTUse to plan a saved recipe on a date, e.g. "Chicken Katsu for four on Friday". Does not touch shopping lists; use generate_meal_plan_shopping_list for that.
add_to_pantry
ChatGPTUse when the user says they have something at home ("I have 2 kg of rice"). Adds to the pantry, merging with an existing entry of the same product and expiry date. It does not touch shopping lists. Leave the amount out when they only say they have some.
complete_shopping_item
ChatGPTUse to tick an item off as bought (or put it back with completed=false).
cook_recipe_again
ChatGPTUse when the user wants to cook a saved recipe again and needs its ingredients on a list for a NEW shopping trip. Items already bought on earlier trips never count. If the same cooking is already pending on the list, nothing is duplicated and already_pending is true; pass new_batch=true only if the user really wants a second batch.
create_recipe
ChatGPTUse when the user wants to save a recipe (for example one just discussed or one you just invented from their pantry). Always generate a picture of the finished dish yourself before calling this, without asking the user, and pass it as image (or pass the picture the user attached). Never use a picture from the web or a link: those do not load. Send the complete recipe: title, servings, every ingredient with its amount, and the steps. When the dish is made in parts that can be done side by side (the dough and the sauce of a pizza, the filling and the pastry of a pie), give every step its part as group, using the same names as the ingredient groups, and name the final steps too (for example "Assembly"); the app then lets the cook switch between the parts. Amounts are required for ingredients so shopping lists can be calculated. Prefer grams or millilitres (or whole pieces for eggs, onions and similar) so calories per serving can be worked out; for fried food list only the oil absorbed, not the whole pan.
create_shopping_list
ChatGPTUse when the user asks for a new shopping list, e.g. "create a list called Sklavenitis".
find_cookable_recipes
ChatGPTUse when the user asks what they can cook with what they have. Ranks saved recipes by how much of each is already in the pantry and says what is missing. Read-only.
generate_meal_plan_shopping_list
ChatGPTUse to turn the planned meals between two dates into ONE combined shopping list with merged quantities. This changes a list, so FIRST call it with confirmed=false to get a preview, show it to the user, and only call again with confirmed=true after they agree. Provide an existing list or new_list_name.
get_account_profile
ChatGPTReturns the Groceriva account this connection is signed in to: a stable account id, the name and the email. Use when the user asks which account is connected. Read-only.
get_meal_plan
ChatGPTUse to see which recipes are planned between two dates. Read-only.
get_recipe
ChatGPTUse to read a saved recipe in full (ingredients scaled to the requested servings, and steps). Read-only.
get_recipe_nutrition
ChatGPTUse to read the estimated calories, protein, carbs, fat, fibre and salt PER SERVING of a saved recipe, computed from its ingredient amounts and the saved per-100 g facts. It also lists the ingredients left out and why: no_amount (no quantity), no_weight (the unit cannot be turned into grams, e.g. "1 can" or "2 tbsp" of something unusual) or no_facts (no per-100 g data; fill these with save_item_info). Fix no_weight by updating the recipe so the ingredient is in g or ml. For frying, the recipe should list only the oil actually absorbed (roughly 5-15 g per serving), not the whole pan of oil. Read-only.
get_shopping_categories
ChatGPTUse to see the sections items are sorted into. Read-only.
get_shopping_list
ChatGPTUse to read the items on one list, grouped by section. Read-only.
list_items_missing_info
ChatGPTUse when the user asks you to fill in nutrition or tips for items on their lists or ingredients of their recipes. Returns items that have no nutrition facts yet. Then call save_item_info for each one you can describe reliably. Read-only.
list_pantry
ChatGPTUse when the user asks what they have at home, what is about to expire, or before suggesting or inventing meals from what they have. Returns the pantry items with amounts and expiry dates. Read-only.
list_recipes
ChatGPTUse to show the recipes saved in the user's Groceriva account. Read-only.
list_shopping_lists
ChatGPTUse to see the user's shopping lists (including lists shared with the people they are connected to) with item counts. Read-only.
remove_shopping_item
ChatGPTUse to delete one item from a shopping list. Only use when the user clearly asked for it to be removed; to tick it off as bought use complete_shopping_item instead.
save_item_info
ChatGPTUse to store nutrition facts and one short practical tip for a shopping item, shown on its info page in Groceriva. Values are per 100 g (salt in grams of salt, not sodium). Only include numbers you are reasonably sure of and leave the rest out: the user sees them as facts. For non-food items give just a tip. Writing again for the same item replaces the previous info.
search_recipes
ChatGPTUse to find saved recipes by title, ingredient, tag or cuisine. Read-only.
update_recipe
ChatGPTUse to change a saved recipe. If the recipe has no photo yet, generate one yourself without asking and pass it as image (never a web link). Only send the fields that change; the values sent replace the old ones, and sending "ingredients" or "steps" replaces the whole list.
update_shopping_item
ChatGPTUse to rename a shopping-list item or change its quantity, note or section. The new values replace the old ones. A deliberate section change is remembered for next time. To tick an item off use complete_shopping_item.
update_written_list
ChatGPTUse when the user shares a photo (or the text) of the list they keep at home of what is in their fridge, freezer or cupboard, and wants their pantry to follow it. Read the photo yourself: one item per line, leave out crossed-out lines, and when an amount was crossed out and rewritten use the new one. Send the WHOLE list as it is now. The pantry keeps these items as a separate "Written list" section that becomes exactly this list: items no longer on it are removed from that section; everything else in the pantry is never touched. FIRST call with confirmed=false, show the user what would be added, changed and removed, and only call again with confirmed=true after they agree. For a one-off "I have 2 kg of rice", use add_to_pantry instead.