Skip to main content
Glama

remove_recipe_from_meal_plan

Destructive

Remove one meal from a meal plan -- requires Subscriber. Only that one slot's entry goes; the recipe stays in My Recipes and in any other slot it fills.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "remove_recipe_from_meal_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, and the description goes beyond them by bounding the blast radius precisely: only that one slot's entry is removed, while the recipe persists in My Recipes and in any other slot it fills. It also adds an authorization requirement (Subscriber), which the annotations cannot express.

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 sentences, front-loaded with the action, followed by the essential scoping caveat. No filler and nothing that could be trimmed without losing information.

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 two-parameter destructive tool with full schema coverage and annotations covering the safety profile, the description supplies the two things structured fields cannot: the subscription prerequisite and the exact extent of the deletion. Nothing needed 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already explains that entry_id comes from a plan's grid or add_recipe_to_meal_plan and is not the recipe id, plus the session_token/Authorization alternative. The description adds nothing on parameters, so the baseline 3 applies.

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 ('Remove one meal from a meal plan') and immediately scopes it to a single slot, which distinguishes it from sibling tools like remove_recipe_from_my_recipes and remove_recipe_from_grocery_list. An agent can tell what is being removed and what is not.

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?

'requires Subscriber' gives an explicit eligibility prerequisite, and the statement that the recipe stays in My Recipes implicitly steers the agent away from using this for recipe deletion. It does not, however, name the alternative tool (e.g. remove_recipe_from_my_recipes) or state when-not to call it, so routing is left partly to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources