Chop it: meal planning, recipes, pantry and shopping

Widget session

get_widget_session

Read-only

Used by the Chop it widget itself to load screens. Never call this; it returns nothing useful in chat.

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": "get_widget_session"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`token`	No
`userId`	No
`signedIn`	Yes
`expiresAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond the read-only and non-destructive annotations, it discloses that the tool supports widget screen loading and has no useful chat return value. Further session or screen-loading mechanics are omitted, but those details are largely unnecessary because chat agents are explicitly told not to invoke 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?

Two short sentences efficiently convey the intended consumer, function, prohibition, and rationale. The internal-only context is front-loaded, and there is no redundant or unnecessary wording.

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 zero-parameter internal utility, the description supplies everything an agent needs for correct selection: it is widget-only and should not be called in chat. The presence of an output schema means the description does not need to document return fields.

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?

The tool has no parameters, so there are no argument semantics for the description to clarify. This meets the baseline for a zero-parameter tool without introducing irrelevant invocation details.

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 identifies the tool's specific role: the Chop it widget uses it to load screens. Its internal-widget scope clearly distinguishes it from the user-facing recipe, menu, pantry, and shopping-list siblings.

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 provides explicit usage guidance with 'Never call this,' while also identifying the intended caller as the widget itself. The reason, that it returns nothing useful in chat, makes the exclusion actionable rather than arbitrary.

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?