create_meal_plan
Plan a meal for a specific date and meal type. Provide recipeId to link an existing recipe (from list_recipes) OR name for a custom meal; when recipeId is given any name is ignored and stored as null.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"date": "2026-10-28",
"mealType": "dinner",
"recipeId": "8f14e45f-ceea-467e-8a2f-1a2b3c4d5e6f",
"servings": 4
},
"name": "create_meal_plan"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Date, YYYY-MM-DD. Must be today or within the next 28 days, so work it out from today's date. | |
| name | No | Custom meal name when no recipe is linked. | |
| notes | No | Free-text notes. | |
| mealType | Yes | Meal slot of the day. | |
| recipeId | No | Recipe id from list_recipes or list_global_recipes. | |
| servings | No | Servings, 1-100. | |
| recipeSource | No | Use 'global' when recipeId came from list_global_recipes. Defaults to 'household'. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| title | No | ||
| message | No | ||
| variant | No |