Cookidoo MCP Server

Overview Schema Source Related Servers Discussions Admin

Remove From Meal Plan

remove_from_meal_plan

Destructive

Remove selected recipes from a specific day of your meal plan without deleting the recipes themselves. Use it to adjust daily plans while keeping recipe records intact.

Instructions

Remove recipes from one day of the meal plan. The recipes themselves are not deleted.

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": {
      "day": "<day>"
    },
    "name": "remove_from_meal_plan"
  }
}

Input Schema

Name	Required	Description
`day`	Yes	The day, as YYYY-MM-DD
`recipe_ids`	No	Cookidoo catalogue recipe IDs planned on that day
`custom_recipe_ids`	No	IDs of the user's own custom recipes planned on that day

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description usefully narrows that: the recipes are not deleted, only their plan slots. It stops short of saying whether omitted ID lists clear the whole day or whether the removal is reversible, which matters for a destructive operation.

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, both earning their place: the first defines the action and scope, the second pre-empts the most likely misunderstanding. Front-loaded with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema and full annotation set carry much of the burden, but for a destructive tool the description leaves a real behavioral hole: both ID lists are nullable, and it never explains whether passing neither clears the entire day.

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%, so the day format and the two ID-list parameters are already documented in the schema. The description adds only the implicit mapping of 'one day' to the day parameter and says nothing about how the two ID lists interact or what null means.

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 (remove), a specific resource (recipes), and the scope (one day of the meal plan). The second sentence explicitly bounds the effect — only the plan entry goes, not the recipe itself — which separates it from deletion-oriented siblings like delete_custom_recipe.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The context of use is implied by the name and description (pruning a day's plan), but there is no explicit when-to-use versus when-not guidance and no sibling is named as an alternative. It also never states the precondition that at least one of recipe_ids/custom_recipe_ids should be supplied.

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