Chop it: meal planning, recipes, pantry and shopping

Open Chop it

open_chopit

Read-onlyIdempotent

Opens the interactive Chop it app for an explicit request such as 'open Chop It', 'load the app' or 'show my This Week screen'. view selects this_week, saved_weeks, recipes, pantry, shopping or meal_planning. Returns the new app shell where enabled, otherwise a normal browser link. Reads and writes no account data and creates no draft. Available without an account; private screens require sign-in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "open_chopit"
  }
}

Input Schema

Name	Required	Description	Default
`view`	No		this_week

Output Schema

Name	Required	Description	Default
`type`	Yes
`view`	Yes
`appUrl`	Yes
`message`	Yes
`embedded`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description adds genuine behavior: it returns the app shell where enabled, otherwise a plain browser link, touches no account data, and creates no draft. Auth requirements are also disclosed. What 'where enabled' means and why the fallback occurs is left unexplained, keeping it off a 5.

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?

Four tight sentences, front-loaded with purpose, then view values, then return behavior, then auth. Every sentence carries information, though the enumeration of view values is compressed into a single clause that reads slightly like a schema dump.

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 one-optional-param opener with an output schema and full annotations, the description covers purpose, routing, enum meaning, return shape fallback, data-safety, and auth. Nothing an agent needs in order to call it correctly is missing.

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

Parameters5/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 parameter alone, and it does: it enumerates all six valid view values and anchors them to a real intent example ('show my This Week screen'). That is meaningful semantic guidance the bare enum does not provide.

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

Purpose4/5

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

The description opens with a specific verb and resource ('Opens the interactive Chop it app') and scopes it to an explicit user request, which separates it from data-reading siblings like get_my_week or open_saved_week. It does not explicitly name those siblings as alternatives, so it stops short of a 5.

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?

Concrete trigger phrases ('open Chop It', 'load the app', 'show my This Week screen') tell the agent exactly what user intent should route here, and the note about account-free availability versus sign-in-gated private screens adds a real usage condition. It never states when NOT to use it or which sibling to pick for a specific saved week instead.

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?