Chop it: meal planning, recipes, pantry and shopping

Find saved weeks

list_saved_weeks

Read-onlyIdempotent

Lists the user's Saved Weeks with their dinners and savedWeekId, for browsing or picking a week to reuse. Pass nextOffset as offset until hasMore is false to read all weeks. Collect all pages before editing; restart if records change during the read. A week saved earlier in this conversation is identified by the savedWeekId save_week returned, not by its position or recency in this list. Provenance is not recorded for personal snapshots; never infer Chef IQ origin from a title. Read-only. Requires a linked Chop It account.

Input Schema

Name	Required	Description	Default
`offset`	No	Start at 0, then pass nextOffset from the previous page. Read every page before proposing whole-library changes; restart if records change while browsing.

Output Schema

Name	Required	Description	Default
`note`	Yes
`total`	No
`weeks`	Yes
`offset`	No
`hasMore`	No
`pageSize`	No
`returned`	No
`nextOffset`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 1, 2026

addedOutput schema / properties / weeks / items / properties / provenance
```
Added value: +{
+  "const": "not_recorded",
+  "type": "string"
+}
```
addedOutput schema / properties / weeks / items / properties / sourceCollectionId
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / weeks / items / required

Previous value: -[
-  "savedWeekId",
-  "title",
-  "appUrl",
-  "dinnerCount",
-  "servings",
-  "updatedAt",
-  "previewRecipes",
-  "heroImageUrl"
-]New value: +[
+  "savedWeekId",
+  "title",
+  "appUrl",
+  "dinnerCount",
+  "servings",
+  "updatedAt",
+  "previewRecipes",
+  "heroImageUrl",
+  "sourceCollectionId",
+  "provenance"
+]

First observedNov 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond readOnly/ idempotent annotations, it discloses an auth precondition ('Requires a linked Chop It account'), a consistency hazard ('restart if records change during the read'), and a data-provenance limitation ('Provenance is not recorded for personal snapshots'). Those are exactly the non-obvious traits an agent could otherwise get wrong.

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?

Front-loaded with purpose, then paging protocol, then identity/provenance caveats — no filler sentences. It is slightly dense for a one-parameter list tool, but each sentence carries a distinct operational or safety constraint.

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?

Covers the full set of things an agent needs before calling: what comes back at a high level, how to page to exhaustion, the auth prerequisite, and how to match a week to a prior save. With an output schema present and annotations carrying the safety profile, nothing material is missing.

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 100%, so the offset parameter is already documented, and the description reinforces the contract by explaining the nextOffset/hasMore loop rather than repeating the field type. It adds pagination protocol (must read all pages, restart on change) that the schema alone does not convey.

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 ('Lists the user's Saved Weeks') and names the returned payload fields (dinners, savedWeekId), which separates it from siblings like list_saved_recipes or get_my_week. The purpose sentence ('browsing or picking a week to reuse') ties the read to an actual downstream intent.

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?

Gives a concrete when-to-use framing (browsing, picking a week to reuse) plus procedural rules: page with nextOffset until hasMore is false, and collect all pages before editing. It also cross-references save_week as the source of the savedWeekId and warns against identifying weeks by position or recency. It stops short of naming an explicit alternative tool for a different listing need, so it is clear context without full alternative routing.

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?