Skip to main content
Glama
Sign In

Recipe Reels

by com.recipe-reels
OverviewDiscussionsAdmin

keep_meal_plan_entry

Idempotent
Mark a cooked meal in an AI plan as kept, so generate_ai_meal_plan
leaves it in place, or un-keep it -- requires Subscriber. Only an entry
with role "cook" can be kept: prep days and prep meals use the recipe
the household chose for them, so regenerating never replaces them.
Returns the entry's `entry_id` and its new `locked` value.

Input Schema

NameRequiredDescriptionDefault
keepNoTrue to keep the meal through regenerating; False to let regenerating replace it.
entry_idYesOne meal's `entry_id` inside a plan's `grid` (get_my_meal_plan or get_meal_plan_details), or from add_recipe_to_meal_plan's result. Not the recipe's id.
session_tokenNoThe session token check_agent_connection returned for the connected account. Required, unless it's sent as an Authorization: Bearer header on the MCP request instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses Subscriber requirements, the role "cook" eligibility constraint, the regeneration behavior for prep days and prep meals, and the returned entry_id and locked value. The mutation and idempotent behavior are consistent with readOnlyHint=false and idempotentHint=true.

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 effect, then follows with eligibility constraints and return values. Every sentence contributes useful information, with no redundant restatement of the tool name.

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 three-parameter mutation tool with full schema coverage and no output schema, the description provides sufficient context: prerequisites, eligibility rules, effect on regeneration, and return values. Nothing critical is missing for correct invocation.

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 baseline is 3. The description adds meaningful parameter-related context by stating that only entries with role "cook" can be kept and that the operation returns the entry's entry_id and new locked value, which helps the agent interpret entry_id and the effect of the keep flag.

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: marking a cooked meal in an AI plan as kept or un-kept. It directly ties the action to the sibling tool generate_ai_meal_plan and explains the intended effect, so an agent can distinguish it from plan-reading or recipe-editing siblings.

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?

The description explains when to use the tool: to make generate_ai_meal_plan leave a cooked meal in place, or to let regeneration replace it. It also states prerequisites and constraints, including Subscriber access and the role "cook" requirement. It does not explicitly name fallback alternatives for ineligible entries, but the usage context is clear.

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

All Recipe Reels toolsInspect
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