weReci

Put things ON the user's own shopping list (List It) — the running list they carry in the app. Call it ONLY when the user explicitly asks to add, save, or collect for later ("put those on my list", "save the ingredients for Sunday", "also add paper towels") — never speculatively, and never as a follow-up they didn't ask for. Pass recipes by id in recipe_ids (their ingredient lines go on), and/or plain one-off items in items ("paper towels", "2 lemons") — at least one of the two. This tool only COLLECTS: to propose a consolidated list or hand one off for shopping (cart, email), use build_shopping_list instead. Re-adding a recipe replaces its lines (safe to repeat). Pass pantry staples the user keeps in 'exclude' and mention what you skipped. recipe_ids MUST be copied exactly from search_recipes hits, the retrieved set, or list_conceits members — never invented. share decides WHERE the lines go: the user's shared list (visible to Home Assistant and a cookbook partner) or the list on their phone; leave it out unless they said.

Compose a consolidated grocery list from 1-8 recipes in the collection and hand it off for shopping — nothing is stored; the list is an artifact of this conversation. ALWAYS call with mode 'propose' first and show the user the returned list. Only after they explicitly approve in a LATER turn may you call a send mode: 'cart' (adds the items to their own linked Kroger-family cart — Fred Meyer, Mariano's, Ralphs… — requires the grocery:cart permission; asks them to connect their Kroger account the first time), 'coupons' (Pete's Fresh COUPON mode — clips this week's matching specials to their loyalty card; it can ONLY match items currently on coupon, so most items staying unmatched is normal; same grocery:cart permission) or 'email' (mails them the list, forwardable to whoever shops — requires the email:send permission). NEVER propose and send in the same turn. Pass pantry staples they keep in 'exclude'. recipe_ids MUST be copied exactly from search_recipes or list_conceits results — never invented.

Explain HOW two things in the archive are related: the shortest chain of relationships between any two nodes — two recipes (shared cookbook? shared ingredient?), a person and a recipe, an appliance and an author. Returns the labeled path or reports they're unconnected. Node ids are ':' — e.g. 'entry:' (prefix a search_recipes hit id with 'entry:'), 'ingredient:brown-sugar', 'author:mother-in-law', 'appliance:oven', 'user:'. User-supplied metadata is traversable too: 'tag:' (a shared free-form label) and 'property::' (a shared key=value, e.g. 'property:region:alaska') — every entry carrying that tag/value links to the same node. Recipes with named sub-preparations carry 'component::' nodes (HAS_COMPONENT from the entry; the component links to its own ingredients/steps) — e.g. "what else uses this sauce?" is one hop.

Check a job started with start_background_job. Returns state "running", "done" (with the run's result) or "failed" (with the reason). A run whose invocation died is reported as failed rather than left running forever, so it is safe to poll until this stops saying running.

Everything directly connected to one node, grouped by relationship: an entry's author/owner/source/ingredients/appliances/tools, an author's works, an ingredient's recipes, a user's collection. Exact and complete (unlike semantic search). Node ids are ':' — e.g. 'entry:' (prefix a search_recipes hit id with 'entry:'), 'ingredient:brown-sugar', 'author:mother-in-law', 'appliance:oven', 'user:'. User-supplied metadata is traversable too: 'tag:' (a shared free-form label) and 'property::' (a shared key=value, e.g. 'property:region:alaska') — every entry carrying that tag/value links to the same node. Recipes with named sub-preparations carry 'component::' nodes (HAS_COMPONENT from the entry; the component links to its own ingredients/steps) — e.g. "what else uses this sauce?" is one hop.

Fetch one entry's full details by its id — ids come from search_recipes or list_conceits results. Recipes return title, ingredients, instructions, notes and photo URL; non-recipe entries (letters, emails — list_conceits members carry a kind field) return the same shape with entry_kind set.

Read the user's SYNCED shopping list — the shared List It list they keep with their cookbook partner: every line, whether it's crossed off, its aisle, and which recipes it came from. Use it to answer "what's on the list?" or before ticking things off. The list kept only on the user's phone is NOT visible here; when available is false, say why in one sentence (the note) and don't retry. Pass since (the last seq you saw) to get a cheap unchanged answer when nothing moved.

List the collection's current curated shelves (themed groups spanning all entry kinds) with their titles, descriptions, cover photos, and members (each member: id, kind [recipe/letter/email], title, photo URL; Wikipedia ingredient reference cards are flagged reference: true). Build a member's app link by substituting its id into app_url_template. unavailable_count reports members that no longer resolve.

Regenerate the collection's curated shelves ("conceits") — a fresh themed re-grouping of every entry, replacing the current shelves. BEFORE calling: confirm the user actually wants a reshuffle, and ask whether they'd like to give the curation a creative direction (a theme, mood, or organizing idea — e.g. "lean into late-summer produce"). Pass their answer as guidance, or omit it for a clean-slate shuffle. The run takes about a minute in the background; call list_conceits afterwards to see the new shelves.

Search the recipe collection semantically (dense + ColBERT hybrid) to gather the members of a theme. Pass a rich natural-language concept, not just a keyword — e.g. 'cozy cold-weather baked desserts', 'bright summer salads with fresh vegetables', 'Latin American and Caribbean mains', 'anything featuring apples'. Returns up to limit compact hits {id,title,cuisine,dietary,cookbook}. Call once per theme concept; call again with a broader/narrower query if a group is too small or too big. Do NOT rely on cuisine labels alone — many recipes are unlabelled and only reachable by concept search.

Email a recipe from the collection to YOU — the signed-in account. There is no recipient option: it always goes to your own verified email, never anyone else (to share with others, forward it or use a share link). Optionally include a short personal note. Requires the email:send permission.

Start a long-running background job and get a job id to poll with get_background_job. Use this for work that takes minutes rather than seconds. Available kinds: "conceit_reshuffle" — Regenerate the collection's curated shelves ("conceits") — a fresh themed re-grouping of every entry, replacing the current shelves. Takes several minutes. Confirm with the user before starting one: these runs cost real money and replace existing work.

Multi-hop graph walk from a start node, with filters. This is the EXACT-enumeration tool: 'every recipe using brown sugar' (start='ingredient:brown-sugar', node_types=['entry']), 'all of Grandma's recipes' (start='author:...', node_types=['entry']), 'the ingredient fingerprint of mom's collection' (start='user:...', depth 2, node_types=['ingredient']). Results are complete up to limit — if truncated, the response says so. Node ids are ':' — e.g. 'entry:' (prefix a search_recipes hit id with 'entry:'), 'ingredient:brown-sugar', 'author:mother-in-law', 'appliance:oven', 'user:'. User-supplied metadata is traversable too: 'tag:' (a shared free-form label) and 'property::' (a shared key=value, e.g. 'property:region:alaska') — every entry carrying that tag/value links to the same node. Recipes with named sub-preparations carry 'component::' nodes (HAS_COMPONENT from the entry; the component links to its own ingredients/steps) — e.g. "what else uses this sauce?" is one hop.

Change the user's SYNCED shopping list (see get_shopping_list): cross lines off, un-cross them, take them off, or add plain one-off lines. Call it ONLY on the user's explicit ask ("tick off the milk", "take eggs off the list"). check / uncheck / remove take item keys copied exactly from get_shopping_list — never invented. add takes plain lines as the user said them ("paper towels"). Their partner sees every change. To put a RECIPE's ingredients on the list use add_to_shopping_list instead. Returns the list as it now stands.