Skip to main content
Glama

Strega Recipes

Order the groceries for delivery

order_groceries

Send a shopping list to a grocer near the cook: into their cart where the store allows it (King Soopers and other Kroger stores, once connected), else one list link, else a search link per item. Use when the cook says "order these", "get it delivered", "send it to my store". No saved store: it asks their ZIP, then lists nearby grocers (choose_store); call again with store and zip, which saves it. A cart grocer first returns cart_preview: tell the cook its say (flagged items and total only), apply their changes as edits, then call with preview_id and confirm: true. Share share_url with the cook (the order is theirs: Strega's order page uses their saved store and sign-in); list_url is the link for the household. Strega never picks a brand. Keep commission_disclosure in parentheses right after the link, once.

Input Schema

NameRequiredDescriptionDefault
zipNoThe cook's ZIP code, when they gave it; saved with their store. Never guess it
editsNoThe cook's changes to a preview ("skip the hoisin", "2 salmon"), with preview_id
storeNoThe store the cook picked or named ("Sprouts", "King Soopers"), ideally one from choose_store. Saved as their store unless remember_store is false
unitsNoUS cups/oz/°F or metric grams/ml/°C. Defaults to the cook's setting.
pantryNoIngredients the cook already has; they are not ordered
confirmNotrue, with preview_id, once the cook said yes to the preview
list_idNoId of a saved list from build_shopping_list or plan_meals
previewNoA cart grocer previews before adding anything (the default). false adds straight away, only when the cook said they don't need to check
recipesNo
providerNoGrocer to hand the list to: instacart, walmart, kroger, amazon or search. Omit for the cook's saved store, or Instacart when that store isn't available. An unknown or unavailable grocer returns an error listing the available ones.
preview_idNoA cart_preview's id: with edits it updates the preview, with confirm: true it adds exactly those items to the cart
remember_storeNofalse for a one-off order elsewhere; the saved store stays as it was

Output Schema

NameRequiredDescriptionDefault
urlNoThe grocer's link for the whole list (through Strega's /go redirect), or null when each item has its own search link
asksNoAt most one question for the cook, with a home in preferences
linkNoThe cook has to connect (or reconnect) a retailer account first
modeNoOne link to the whole list, a cart, or a search link per item
noteNoThe store sentence to read out
guideNoHow to answer this turn: rules for you, the assistant, not words for the cook. Follow them before anything else here (#258)
linesNo
storeNoThe cook's saved store, when set; they still pick the store at checkout
list_idYesThe saved list the order came from
noticesNoAt most one note about Strega to pass on when there's room (one per cook per week; off with workflow whats_new: off)
adjustedNoDefaults 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
list_urlYesThe list on Strega
providerNoThe grocer the list went to; never ranked by commission
share_urlYesThe one link to give the cook: their order at the grocer, or Strega's order page (the cook's own: it uses their saved store and needs their sign-in) while they pick a store. For the household, share list_url
next_stepsNoSuggestions, 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
connect_urlNoStarts the retailer sign-in; present with link
cart_previewNoA cart grocer's preview (#227): nothing is in the cart yet. Tell the cook its say (flagged lines and the total only), apply their changes with edits, then call again with preview_id and confirm: true. The handoff fields are absent
choose_storeNoNo store saved yet: nothing was sent. Ask the cook which grocer (or their ZIP first), then call again with store and zip. The handoff fields are absent
skipped_pantryNoLeft off the order: in the cook's pantry
unmatched_productsNoLines that didn't match a product when the rest went into a cart
commission_disclosureNoPresent when the links are affiliate links: keep it in parentheses right after the link, once; don't expand on it unless the cook asks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare this is not read-only and is open-world, but the description adds substantial behavior: cart previews, confirmation, saved-store behavior, share URLs, sign-in ownership, and commission disclosure placement. It clearly explains what side effects occur before and after ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the action and then follows the ordering workflow, but it is dense and parenthetical. Most sentences earn their place for a complex 12-parameter tool, though slightly more structure would improve readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity, high schema coverage, output schema, and annotations, the description covers the key workflow an agent needs: when to use it, how saved stores work, when previews and confirmations are required, and how to share results. Nothing critical is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is very high at 92%, so parameter meanings are mostly already documented. The description still adds workflow semantics for preview_id, confirm, edits, store, and zip saving, which helps an agent understand how parameters interact across calls.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: sending a shopping list to a grocer for delivery. It distinguishes the tool from list-building siblings by explaining that it hands a list to a grocer, and it names the cart/list-link/search-link outcomes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit trigger phrases such as "order these" and "get it delivered", plus the no-saved-store flow and the preview-before-confirm workflow. It does not explicitly say when to use sibling tools like build_shopping_list instead, but the ordering context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources