Skip to main content
Glama
smeet666

mcp-recipes

Scale an ingredient list, in either language

scale_ingredients
Read-onlyIdempotent

Rescale ingredient lists for any servings or factor in French or English, with kitchen-friendly rounding that keeps eggs whole and adjusts spoons and pinches realistically.

Instructions

Multiply a list of ingredient lines, in French, in English, or in a list holding both. Give either 'factor', or 'from_servings' and 'to_servings' and the factor is worked out from them. Quantities land where a kitchen can follow them: an egg stays whole because half of one is not something a cook takes out of the shell, while anything that pours, weighs or cuts can halve, a spoonful shrinks into the smaller spoon before it is rounded, and a pinch keeps whatever size a hand gives it while its count is multiplied. Every line comes back with 'scaling': 'scaled' when the arithmetic landed on the exact product, 'rounded' when something had to move for the line to stay usable, 'unscaled' when the line carries nothing to multiply. A rounded line says what it was rounded from and in which direction. No quantity is converted between measuring systems: grams stay grams and cups stay cups, because a conversion changes what the recipe said.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factorNoWhat to multiply by. Give exactly one of: 'factor', or both 'from_servings' and 'to_servings'.
languageNo'auto' reads each line on its own, which is what a list holding both languages needs. Name a language to read every line that way.auto
ingredientsYesThe lines as written, one ingredient each, such as '200 g de farine' or '3 eggs'. One line, not a whole recipe.
to_servingsNoWhat it should serve. Give it with 'from_servings', and without 'factor'.
from_servingsNoWhat the list serves now. Give it with 'to_servings', and without 'factor'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
factorYesWhat every quantity was multiplied by.
languageYesHow the lines were read.
ingredientsYes
scaled_countYesLines whose arithmetic came out exact.
rounded_countYesLines whose value moved to stay usable.
unscaled_countYesLines carrying nothing that can be multiplied.
Behavior5/5

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

Beyond the readOnlyHint and idempotentHint annotations, the description discloses rich behavioral traits: rounding rules ('an egg stays whole', 'a spoonful shrinks into the smaller spoon'), the exact 'scaling' status values ('scaled', 'rounded', 'unscaled'), and the constraint that no quantity is converted between measuring systems. This provides significant added value for predicting tool behavior.

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 structured with a clear opening statement of function, followed by input guidance, then detailed behavioral rules. Every sentence contributes unique information—from language support to output scaling categories to the no-conversion constraint—without unnecessary repetition. It is detailed yet efficiently organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity and the presence of an output schema, the description covers all essential aspects: language handling, parameter alternatives, rounding behavior, scaling statuses, and conversion constraints. The agent has enough information to select and invoke the tool correctly, and with the output schema available, return values do not need to be re-explained.

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 already describes all parameters with 100% coverage, including the factor/servings exclusivity. The description reinforces this relationship and adds context about output rounding, but it does not add substantial new meaning to individual parameters beyond what the schema provides. Baseline 3 is appropriate.

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 clearly states the tool's purpose: 'Multiply a list of ingredient lines' in multiple language contexts. This specific verb-resource pairing distinguishes it from sibling tools like get_recipe, search_recipes, and compare_recipes, which focus on retrieval and comparison rather than scaling.

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

Usage Guidelines4/5

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

The description explicitly explains the two input modes: give either 'factor', or 'from_servings' and 'to_servings', and clarifies that the factor is worked out from servings. It does not mention alternative tools or exclusions, but the context for using this scaling tool is clear and directly actionable.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-recipes'

If you have feedback or need assistance with the MCP directory API, please join our Discord server