ReciPal MCP by usefulapi

Create recipe with ingredients

recipal_create_recipe_from_ingredients

Destructive

WRITE: create a new recipe and its ingredient lines in one call. ingredients lists ingredient ids with the weight of each in grams. Optional yield, servings and packaging fields as in recipal_create_recipe. Creates a record in your ReciPal account. POST /recipes/shortcut.

Input Schema

Name	Required	Description
`sku`	No	Your SKU.
`name`	No	Recipe name.
`packages`	No	Number of packages the recipe yields per batch (0 or more).
`servings`	No	Servings per package (at least 1).
`allergens`	No	Allergens by name, e.g. {"Milk": true, "Almond": true, "other-shellfish": "Oyster"}. Standard names: Wheat, Peanuts, Soy, Sesame, Mustard, Sulfites, Milk (Goat milk, Sheep milk), Egg (Duck egg, Quail egg), Fish (Tuna, Cod, Salmon, Bass), Shellfish (Crab, Lobster, Shrimp), tree nuts (Almond, Cashew, Hazelnut, Macadamia nut, Pecan, Pine nut, Pistachio, Walnut ...), Gluten (Barley, Oats, Rye, Triticale). other-milk/-egg/-fish/-shellfish/-treenut take a free-text source. An empty object {} clears all allergens.
`labor_cost`	No	Labor cost per batch.
`ingredients`	Yes	Ingredient ids with their weights in grams (1-100 lines).
`preparation`	No	Preparation instructions for staff.
`overhead_cost`	No	Overhead cost per batch (rent, electricity, equipment ...).
`packaging_cost`	No	Cost per package of direct and secondary packaging.
`subrecipe_name`	No	Name shown when this recipe is used as a subrecipe in another recipe's ingredient list.
`ingredient_list`	No	Ingredient list text for the label.
`suggested_serving`	No	Suggested serving in common terms, e.g. "1 piece or 1 cup".
`package_yield_unit`	No	Unit of the finished package weight: "grams" (default), "ounces", "mL" or "fluid ounces".
`prepared_serving_note`	No	Note after the serving size on FDA labels, e.g. "makes 1 cup prepared".
`subrecipe_name_french`	No	French name shown when used as a subrecipe.
`package_yield_quantity`	No	Net weight of each finished package, in package_yield_unit (default 0).
`visual_unit_of_measure`	No	Visual reference after the metric serving size on FDA labels, e.g. "5 chips".

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare write, destructive, non-idempotent, and openWorld behavior. The description adds the 'WRITE:' prefix, that a record is created, and the endpoint, but does not disclose auth requirements, rate limits, or what happens on duplicate/invalid ingredient ids — gaps that matter for a destructive mutation.

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?

Four short sentences, front-loaded with the 'WRITE:' marker and the core action. Every sentence carries useful information (action, required ingredient format, optional fields reference, endpoint) with no filler.

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?

Given 18 parameters with 100% schema coverage and full annotations, the description covers the high-level action, required ingredient structure, optional fields, and endpoint. It omits what the call returns (no output schema exists), which would be the one missing piece for a fully complete definition.

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 description coverage is 100%, so the schema already documents all 18 parameters in detail. The description repeats the required 'ingredients' format (ids plus grams) and points to recipal_create_recipe for optional fields, which is mildly helpful but adds little beyond the schema.

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 and its ingredient lines in one call.' The phrase 'in one call' and the cross-reference to recipal_create_recipe hint at differentiation from the sibling, but the definition never explicitly contrasts the two tools' roles.

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 by 'in one call' and the reference to recipal_create_recipe for optional fields, but there is no explicit statement of when to prefer this over recipal_create_recipe plus recipal_add_recipe_ingredient, nor any exclusions or prerequisites.

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

All ReciPal MCP by usefulapi tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create recipe with ingredients

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources