Mealie MCP

create_meal_plan

Create a meal plan entry for a specific date, specifying meal type and optional recipe or title.

Instructions

Create a meal plan entry. date is YYYY-MM-DD. entry_type is breakfast/lunch/dinner/side.

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": {
      "date": "<date>"
    },
    "name": "create_meal_plan"
  }
}

Input Schema

Name	Required	Default
`date`	Yes
`text`	No
`title`	No
`recipe_id`	No
`entry_type`	No	dinner

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Create a meal plan entry' without mentioning side effects, authentication requirements, or whether it overwrites existing entries. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-loading the purpose and key parameter hints. No unnecessary words, though could be structured with bullet points for clarity.

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

Completeness2/5

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

Despite having an output schema, the description omits what the tool returns, how conflicts are handled, and leaves three parameters undocumented. Incomplete for a creation tool with multiple fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

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

Schema description coverage is 0%, so the description should compensate. It explains date format and entry_type values but fails to describe three other parameters (text, title, recipe_id) and their defaults or roles.

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 clearly states the tool creates a meal plan entry and distinguishes its specific parameters (date, entry_type) from sibling tools like add_random_meal_plan or delete_meal_plan. The verb 'create' and resource 'meal plan entry' are precise.

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?

No explicit guidance on when to use this tool versus alternatives such as add_random_meal_plan or when not to use it. The purpose is implied but lacks explicit context on usage scenarios.

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