Agent Chef

Get the shopping list for an online cart

assemble_online_grocery_order

Read-only

Builds the online grocery cart list for this week's recipes: needed items minus pantry stock, grouped with quantities and store, stopping before checkout.

Instructions

Returns the shopping list for filling an online grocery cart: everything this week's selected recipes need minus what is on hand, grouped by item with quantities and which recipe needs it, plus the preferred store. Drive the browser to fill the cart; stop before checkout for approval; then call record_grocery_order.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`week_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`week`	Yes
`items`	Yes
`store`	Yes
`recipes`	Yes
`servings`	Yes
`instructions`	Yes
`skipped_on_hand`	Yes
`shopping_preferences`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.1.1Oct 3, 2026
- addedOutput schema / properties / skipped_on_hand / items / properties / expires_at
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / skipped_on_hand / items / properties / staple
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / week / properties / share_url
```
Added value: +{
+  "description": "Public page showing this week's winners",
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedv0.1.0Sep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral value beyond that: the list is computed as needed-minus-on-hand, it drives a browser step, and it must pause before checkout for human approval. Only the return/pagination format is left unstated, which is minor given the output schema exists.

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

Conciseness5/5

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

Two dense sentences: the first front-loads what is returned and its structure, the second front-loads the workflow. No filler, nothing repeated from annotations or schema.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. What remains — where this fits in the ordering workflow and what to call next — is fully supplied, making it complete for an agent to act on.

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

Parameters3/5

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

There is one parameter (week_id) with 0% schema description coverage, so the description must carry the meaning. It only implies the parameter via 'this week's selected recipes', suggesting a default/current week, without naming or explaining week_id or how to target a different week.

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?

States a specific verb and resource (returns the shopping list for an online grocery cart) and enumerates the payload contents: recipes minus on-hand, grouped by item with quantities and recipe attribution, plus preferred store. This is clearly distinguishable from siblings like record_grocery_order or get_ingredients.

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?

The description gives explicit workflow context: drive the browser to fill the cart, stop before checkout for approval, then call record_grocery_order. It names the downstream sibling and the sequencing constraint. It stops short of saying when this tool should not be used (e.g. before recipes are set), so it is not a 5.

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