Chop it: meal planning, recipes, pantry and shopping

Read a saved week

get_saved_week

Read-onlyIdempotent

Reads every dinner in one Saved Week by savedWeekId, with compact recipe titles and stored serving settings, as data for a chat answer. Keeps unavailable recipe IDs and unknown portions explicit. No app widget, new draft, full recipe hydration or change to This Week. For contents and comparison questions; open_saved_week creates an editable copy when changes or shopping are wanted. Requires a linked Chop It account.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "savedWeekId": "<savedWeekId>"
    },
    "name": "get_saved_week"
  }
}

Input Schema

Name	Required	Description	Default
`savedWeekId`	Yes

Output Schema

Name	Required	Description	Default
`note`	Yes
`title`	Yes
`appUrl`	Yes
`dinners`	Yes
`complete`	Yes
`servings`	Yes
`updatedAt`	Yes
`dinnerCount`	Yes
`savedWeekId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description goes further: it discloses that unavailable recipe IDs and unknown portions are kept explicit rather than dropped, that no full recipe hydration occurs, and that a linked Chop It account is required. Those are real behavioral facts an agent cannot infer from the structured fields.

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?

Sentences are front-loaded with purpose then exclusions then the alternative, and each clause carries information. The telegraphic, article-dropped phrasing ("No app widget, new draft, full recipe hydration") is dense to the point of being slightly harder to parse than necessary.

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?

For a single-parameter read with an output schema, annotations, and a named alternative, nothing material is missing: scope, prerequisites (linked account), non-goals, and change semantics are all covered. Return values are correctly left to the output schema.

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% for the single parameter, and the description only restates that the lookup is "by savedWeekId" without adding format, source, or how to obtain a valid ID. The UUID format lives in the schema, so the description adds little meaning beyond it; this is the minimum-viable tier for a one-parameter tool.

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?

"Reads every dinner in one Saved Week by savedWeekId, with compact recipe titles and stored serving settings" gives a specific verb (reads), a precise resource (one Saved Week), and the shape of what comes back. It also names the sibling it is not (open_saved_week), so an agent can separate the read path from the editable-copy path without opening either schema.

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?

"For contents and comparison questions" states when to use it, and "open_saved_week creates an editable copy when changes or shopping are wanted" states the alternative and the condition that selects it. Negative exclusions (no widget, no new draft, no change to This Week) reinforce the boundary.

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.

Resources

Need Help?