grocy-mcp

Recipe Create Tool

recipe_create_tool

Create a new recipe in Grocy by providing a name, optional instructions, and an ingredient list with product IDs and amounts to manage household cooking.

Instructions

Create a new recipe in Grocy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Recipe name (e.g. "Banana Bread").
`description`	No	Optional description or instructions for the recipe.
`ingredients`	No	JSON array of ingredient objects. Each object should have "product_id" (integer) and "amount" (number). Use stock_search_tool to find product IDs. Example: '[{"product_id": 1, "amount": 2}, {"product_id": 5, "amount": 0.5}]'.	[]

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 15, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only restates the basic create action and does not mention side effects, whether a created recipe can be edited later, required permissions, or what the operation returns.

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?

The description is a single efficient sentence with no filler. It is front-loaded and easy to process, though it is arguably brief to the point of omitting useful usage and behavioral context.

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?

The input schema fully documents the three parameters and an output schema is present, so invoking the tool is possible, but the description alone is only minimally viable. It lacks any mention of when to choose this tool over recipe_create_by_name_tool and gives no behavioral context for a mutating 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?

The schema covers 100% of parameters with descriptions and examples, so the description does not need to compensate. The description itself adds no parameter meaning beyond what the input schema already provides, which matches the baseline for high schema coverage.

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?

The description clearly states the action and resource: 'Create a new recipe in Grocy.' This is specific enough to identify the tool's purpose from its name alone, but it does not differentiate it from the closely related sibling recipe_create_by_name_tool, which also creates recipes.

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?

The description provides no guidance on when to use this tool versus alternatives such as recipe_create_by_name_tool or recipe_update_tool. There are no stated conditions, exclusions, or sibling comparisons.

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

Deploy Server