Skip to main content
Glama
Sign In
mealie-mcp

mealie-mcp

by proffalken
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_recipe

Retrieves full recipe details—ingredients, instructions, and the exact Mealie page URL—by recipe ID or slug so you can view or link to it accurately.

Instructions

Get full details of a recipe including all ingredients and instructions. Each recipe includes a url linking to its Mealie page; quote it exactly when linking.

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

Input Schema

NameRequiredDescriptionDefault
recipe_idYesThe recipe slug or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return contents and a notable convention (each recipe includes a `url` that should be quoted exactly), which is genuine behavioral context, but it is silent on error handling, auth requirements, and whether the read has any side effects.

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 short sentences, front-loaded with the core purpose, and the second sentence carries an actionable linking rule rather than filler. Nothing is redundant, though the linking instruction is only loosely tied to the tool's core retrieval function.

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?

For a one-parameter read tool with no output schema, the description covers purpose, the main returned fields, and a linking convention. The remaining gap is failure behavior for a bad recipe_id, which is minor given the simplicity of the operation.

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%, and the schema already documents recipe_id as 'The recipe slug or ID'. The description adds no meanings, formats, or constraints beyond that, 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 and resource ('Get full details of a recipe') and enumerates what the payload contains (ingredients, instructions). It is clearly a single-recipe fetch by identifier, which implicitly separates it from search_recipes, though no sibling is named explicitly.

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 only implied: an agent can infer this is the tool to call once it has a recipe_id and needs full content rather than a listing. There is no explicit when-to-use, no guidance on obtaining the recipe_id via search_recipes, and no statement about behavior for an invalid slug.

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