Chop it: meal planning, recipes, pantry and shopping

Make a saved week This Week

set_this_week

DestructiveIdempotent

Makes a Saved Week the user's This Week (the week the Chop It app shows for cooking) as an independent working copy with the same servings. Replaces the current This Week; the Saved Week stays reusable. Returns the working copy servings, or null when unset. To change portions, open_saved_week, revise_weekly_menu with servings, save_week, then activate that exact new savedWeekId. Suits a request to make a saved week the current one. Requires a linked Chop It account.

Input Schema

Name	Required	Description	Default
`savedWeekId`	Yes

Output Schema

Name	Required	Description	Default
`state`	Yes
`appUrl`	Yes
`status`	Yes
`message`	Yes
`servings`	Yes
`savedWeekId`	Yes
`recipeServings`	Yes
`activeCollectionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

addedOutput schema / properties / recipeServings

Added value: +{
+  "additionalProperties": {
+    "type": "number"
+  },
+  "type": "object"
+}

addedOutput schema / properties / savedWeekId
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / servings

Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "activeCollectionId",
-  "state",
-  "message",
-  "appUrl"
-]New value: +[
+  "status",
+  "activeCollectionId",
+  "state",
+  "message",
+  "appUrl",
+  "savedWeekId",
+  "servings",
+  "recipeServings"
+]

First observedNov 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds important behavior beyond the annotations: it replaces the current This Week, leaves the Saved Week reusable, creates an independent working copy, and returns the working copy servings or null when unset. This directly supports the destructive and idempotent annotation profile rather than contradicting it.

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?

The description is front-loaded with the core action and side effect, then adds the relevant workflow and prerequisite. It is dense but every sentence provides actionable context for invoking the tool correctly.

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?

Although an output schema exists, the description also mentions the return value and null case. Combined with the auth requirement, replacement behavior, reusability of the source Saved Week, and the portions workflow, it is complete enough for an agent to call this tool correctly.

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?

Schema description coverage is 0%, so the description must carry the burden for savedWeekId. It does clarify that the argument should be the exact new savedWeekId after saving a revised menu, but it does not directly define where to obtain a savedWeekId or restate its UUID format.

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: it makes a Saved Week the user's This Week. It also clarifies that this creates an independent working copy with the same servings, which is enough to distinguish it from sibling tools like open_saved_week or save_week.

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

Usage Guidelines5/5

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

It explicitly says what request it suits and gives a concrete alternative workflow when portions need to change: open_saved_week, revise_weekly_menu, save_week, then activate the exact new savedWeekId. It also names a prerequisite, a linked Chop It account.

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

All Chop it: meal planning, recipes, pantry and shopping tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Directories

Listed in ChatGPT · Chop it

Last observed 2026-11-02

Resources

Need Help?