Groceriva

Use to read a saved recipe in full (ingredients scaled to the requested servings, and steps). Read-only.

get_recipe

Use 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_recipe_nutrition

Use to see the sections items are sorted into. Read-only.

get_shopping_categories

Use to read the items on one list, grouped by section. Read-only.

get_shopping_list

Use 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_items_missing_info

Use 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_pantry

Use to show the recipes saved in the user's Groceriva account. Read-only.

list_recipes

Use to see the user's shopping lists (including lists shared with the people they are connected to) with item counts. Read-only.

list_shopping_lists

Use to tick an item off as bought (or put it back with completed=false).

complete_shopping_item

Use 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.

remove_shopping_item

Use 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.

save_item_info

Use 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_recipe

Use to find saved recipes by title, ingredient, tag or cuisine. Read-only.

search_recipes

Use 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_recipe

Use 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_shopping_item

Use 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.

update_written_list