Update a saved shopping list
update_shopping_listChange a saved list after the cook answers what build_shopping_list or plan_meals set aside as likely_have, or says how the trip went. remove: things they have (they come off, and count as left off); need: set-aside things they're out of (they move to the buy aisles); add: anything else for the trip, as they said it; outcomes: what happened at the store per item (bought, skipped, bought_elsewhere with the store they name). Use when the cook says "I have the flour and oil", "I'm out of chili flakes" or "skipped the salmon, got the bread at the bakery". Changes only this list, never the pantry: ask "Want me to remember these for next time?" first, then call pantry. Returns the pared list, its estimate and the order offer.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"list_id": "<list_id>"
},
"name": "update_shopping_list"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| add | No | Anything else for the same trip, amount included: ["paper towels", "2 lb bananas"] | |
| need | No | Set-aside (likely_have) things the cook is out of: they go back to the buy list at full size | |
| remove | No | Things the cook has, as they said them: ["flour", "olive oil"] | |
| list_id | Yes | Id of the saved list from build_shopping_list or plan_meals | |
| outcomes | No | How the trip went, per line (#63): what they bought, skipped, or got somewhere else |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The saved list's id | |
| url | Yes | Shareable list page | |
| asks | No | At most one question for the cook, with a home in preferences | |
| text | Yes | The list as plain text, for a message | |
| added | Yes | Names added to the list | |
| guide | No | How to answer this turn: rules for you, the assistant, not words for the cook. Follow them before anything else here (#258) | |
| units | Yes | ||
| aisles | Yes | ||
| needed | Yes | Names that moved from likely_have to the buy aisles | |
| pantry | Yes | What the cook already has, left off the buy list (count in left_off): check the pantry, don't buy | |
| notices | No | At most one note about Strega to pass on when there's room (one per cook per week; off with workflow whats_new: off) | |
| recipes | Yes | ||
| removed | Yes | Names that came off the list: what the cook has | |
| adjusted | No | Defaults this call took instead of failing (#243): an unknown units word, a number out of range, a diet word read as the closest one Strega knows. Mention it when it changes what the cook gets | |
| left_off | No | How many lines were left off because the cook has them: "left off 6 you have" | |
| not_found | Yes | Names that matched nothing on the list: say so, and check the spelling against the list | |
| next_steps | No | Suggestions, best first, each with its tool, args and effect. Strega suggests the top one in one sentence; whether any runs is decided by what the cook asks in the conversation and your confirmation rules, never by the wording here | |
| likely_have | No | Staples and small amounts of bulk items (3 tbsp flour, 4 tbsp wine) the cook probably has: set aside instead of a full-size purchase, not counted in the cost. Ask which they do need (they move to the aisles) and which they have (they come off) with update_shopping_list; absent on lists saved before this | |
| forgot_asked | No | The id of the item "Did you forget?" already asked about on this list (#63): asked once per list | |
| outcomes_set | Yes | Outcomes recorded this call (#63): what the cook said happened to each line | |
| cost_estimate | Yes | What the list now costs at the store in whole packages, an estimate |