mealie-agent-mcp

by loidolt

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

Create Meal Plan Entry

create_meal_plan_entry

Add a recipe or free-text entry to a Mealie meal plan for a specified date and meal, with optional notes or title.

Instructions

Add a recipe (or a free-text entry) to the meal plan on a given day.

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": "create_meal_plan_entry"
  }
}

Input Schema

Name	Required	Description	Default
`day`	Yes	Date, YYYY-MM-DD.
`meal`	No	Which meal of the day.	dinner
`note`	No	Optional note.
`title`	No	Title for a free-text entry, e.g. 'Eating out'.
`recipe`	No	Recipe slug or id. Omit for a free-text entry.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-destructive local write. The description adds little beyond that — no mention of duplicate handling, whether the referenced recipe must already exist, or what happens when both recipe and title are supplied.

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?

One sentence, front-loaded with the action and resource, with the free-text alternative packed into a parenthetical. Nothing is wasted and nothing is buried.

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

Completeness4/5

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

With an output schema, full schema descriptions and safety annotations, most of the burden is carried elsewhere; only the recipe-vs-title precedence and the sibling distinction are left unspecified. That is a small gap for a five-parameter create tool, not a blocking one.

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 coverage is 100%, so all five parameters are documented in the schema, including day format, the meal enum with its default, and the 'omit for a free-text entry' guidance on recipe. The description only restates that dual-mode relationship rather than adding new detail such as exclusivity rules or note semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Add') and resource ('meal plan entry'), plus the two accepted content modes (recipe vs free-text). It does not distinguish itself from the sibling 'create_random_meal_plan_entry', which is the one ambiguity an agent would face here.

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?

Usage is implied rather than stated: the parenthetical signals that either a recipe reference or a free-text title is acceptable, which is conditional guidance. There is no explicit when-to-use/when-not or comparison against create_random_meal_plan_entry or delete_meal_plan_entry.

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