Skip to main content
Glama
smeet666

mcp-wikibooks-cookbook

Rescale an ingredient list

scale_ingredients
Read-onlyIdempotent

Rescale English ingredient lists to a target number of servings or a scaling factor, adjusting units and counts for practical cooking.

Instructions

Rescale a list of English ingredient lines. This contacts no website and works on a list from anywhere, including one the user pasted in. Give either 'factor' directly, or 'from_servings' and 'to_servings' and the factor is computed. Grams, millilitres, ounces and pounds are multiplied and rounded to what a scale can show; a quantity that would fall below one is moved to a smaller unit first, so it never rounds away to nothing. Countable things land where a kitchen can follow: an egg, a yolk or a white on a whole one, a clove or a spoon on a half, which is what stops an answer like '2.4 eggs'. An approximate measure is scaled as a count, so a pinch taken from 6 servings to 25 is 4 pinches; the note gives the everyday equivalence, and the quantity stays in the unit the line used. That covers the gestures, such as a pinch, a dash, a glug or a handful, and anything named after what holds it, such as a capful or a spoonful. A line with no quantity at all comes back untouched and flagged. A bracketed equivalent, as in '450 g (1 pound)', is scaled with the amount it restates rather than left to contradict it, and so is one written after a slash, as in '500 g / 1.1 lb'. A line offering a choice, as in '2 tablespoons butter OR 30 g margarine', has both branches scaled, so whichever one the cook takes carries the same share. Prefer this over doing the arithmetic yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factorNoMultiplier to apply. Use this or the from/to pair.
ingredientsYesIngredient lines, for example ['450 g (1 pound) spaghetti', '5 egg yolks', 'Salt'].
to_servingsNoHow many servings are wanted.
from_servingsNoHow many servings the list is written for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
factorYes
ingredientsYes
scaled_countYesLines whose arithmetic came out exact.
rounded_countYesLines whose value was moved to stay usable, not lines that could have been.
unscaled_countYesLines carrying nothing that can be multiplied.
Behavior5/5

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

Annotations declare read-only, open-world, idempotent, non-destructive, and the description adds rich behavioral details: rounding, unit conversion, handling of countable items, approximate measures, no-quantity lines, bracketed equivalents, and choice branches. It also notes it contacts no website, reinforcing read-only.

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?

Every sentence serves a purpose: it defines scope (English, any list), explains modes, and catalogues edge cases in a logical sequence. It is long but appropriately so.

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?

For a tool with this many edge cases, the description covers them all. The output schema exists, so return values need not be described. No gaps found.

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

Parameters5/5

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

Schema has 100% coverage, but description adds the relationship between factor and servings, and explains edge-case behavior that affects parameter interpretation. This goes beyond the schema.

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?

States clearly that it rescales a list of English ingredient lines, with a specific verb and resource. Distinguishes from siblings (recipe lookup tools) by focusing on transformation rather than retrieval.

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?

Explicitly instructs to prefer this over manual arithmetic, and clarifies the two parameter modes (factor vs from/to servings). Context is unambiguous about when to use.

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-wikibooks-cookbook'

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