Skip to main content
Glama
Sign In
mealie-mcp

mealie-mcp

by proffalken
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

create_recipe

Create a new recipe in Mealie with a name, ingredients, and ordered method steps. Add instructions separately from notes to keep the method clear.

Instructions

Create a new recipe in Mealie with ingredients and method steps.

Put the method in instructions, not notes.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe recipe name
notesNoExtra notes (not the method)
source_urlNoOriginal recipe URL
descriptionNoA short description
ingredientsNoIngredients as written, one per string (e.g. '200g flour')
instructionsNoMethod steps in order, one string per step (no numbering needed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a write but says nothing about whether it returns the created recipe, what happens on duplicate names, what permissions are needed, or whether partial payloads (only `name`) are accepted given only one required field.

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 short sentences, the purpose front-loaded and the highest-risk mistake (method in notes) called out immediately. Nothing is wasted or redundant.

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?

Adequate for a simple create tool whose schema is fully documented, but with no annotations and no output schema the description should say at minimum whether the created recipe is returned and how it is identified. That gap matters for an agent that must chain into get_recipe or update_recipe.

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 every parameter is already documented, including the notes/instructions distinction. The description reinforces that distinction, which is mildly useful, but adds no format or structural detail beyond the schema; baseline 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 and resource ('Create a new recipe in Mealie') plus the two payload kinds it accepts (ingredients and method steps). It does not distinguish itself from the sibling create_recipe_from_url, which is the most likely confusion point, so it falls short of a 5.

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

Usage Guidelines2/5

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

No guidance on when to use this versus create_recipe_from_url (importing an existing URL) or update_recipe. The only guidance is about field placement ('put the method in instructions, not notes'), which is parameter-level advice rather than tool-selection advice.

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

Deploy Server

Other Tools