grocy-mcp

Recipe Create By Name Tool

recipe_create_by_name_tool

Create a recipe using product names for ingredients; the system resolves them automatically, avoiding the need to look up IDs.

Instructions

Create a recipe with ingredients specified by product name instead of ID.

This is the easier alternative to recipe_create_tool — you can use product names directly, and they will be resolved automatically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Recipe name (e.g. "Banana Bread").
`description`	No	Optional description or instructions.
`ingredients`	No	JSON array of ingredient objects. Each should have "product" (name string) and "amount" (number). Example: '[{"product": "Flour", "amount": 2}, {"product": "Banana", "amount": 3}]'.	[]

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

A4.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does add useful behavior beyond the schema: product names are resolved automatically rather than passed as IDs. However, it does not mention what happens if a product name cannot be resolved, whether products must already exist, or any other side effects of creation.

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?

The description is compact, front-loaded with the core purpose, and contains no filler. The second sentence earns its place by differentiating the tool from its sibling.

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 a complete input schema and an output schema present, the description covers the key facts an agent needs: what the tool does, how it differs from recipe_create_tool, and how product names are handled. It could add a note about unresolved product names, but that is a minor gap for a simple creation tool.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful semantics by clarifying that the ingredients parameter uses product names rather than IDs and that resolution happens automatically, which goes beyond the raw schema text.

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 states a specific action ('Create a recipe') and the key distinguishing scope: ingredients are specified by product name instead of ID. It explicitly names recipe_create_tool as the alternative, so an agent can immediately tell this tool apart from its sibling.

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

Usage Guidelines5/5

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

It directly says this is 'the easier alternative to recipe_create_tool' and explains when to choose it: when you want to use product names directly, which are resolved automatically. This gives the agent a clear routing signal versus the ID-based sibling.

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

Deploy Server