Skip to main content
Glama
smeet666

mcp-marmiton

Scale an ingredient list

scale_ingredients
Read-onlyIdempotent

Rescale French ingredient lists to any number of servings by factor or from/to serving counts. Handles grams, millilitres, countable items, and approximate measures; flags quantity-less lines.

Instructions

Rescale a list of ingredient lines to a different number of servings, without contacting any website. Give either 'factor' directly, or 'from_servings' and 'to_servings' and the factor is computed. Works on any French ingredient list, whatever its source, so it also serves a recipe the user pasted in. Quantities in grams or millilitres are multiplied and rounded to readable values; a countable thing lands on a half when half of one can be poured, weighed or cut, as a boîte, a sachet, a feuille de gélatine or a cuillère can, and on a whole one when it cannot, as an oeuf, a jaune or a blanc; approximate measures such as a pinch or a handful have their count multiplied in whole units and stay in their own vocabulary. A line writing an article where a digit would go, as in 'un bouchon de rhum' or 'une pincée de sel', is read as one of that measure. Lines carrying no quantity are returned untouched and flagged. 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 ['200 g de farine', '3 oeufs', 'sel'].
to_servingsNoHow many servings are wanted.
from_servingsNoHow many servings the list is written for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
factorYes
ingredientsYes
scaled_countYes
rounded_countYesLines whose value rounding moved away from the exact product, not lines that could have been rounded.
unscaled_countYes
Behavior5/5

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

The description discloses detailed behavior: quantities are multiplied and rounded, countable items are handled with fractions, approximate measures stay whole, and lines without quantities are flagged. This goes beyond annotations (readOnly, idempotent) and fully informs the user of the tool's effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and repetitive. For example, the sentence about countable items and approximate measures is long, and the final sentence about 'A line writing an article where a digit would go' restates earlier content. This could be condensed without losing meaning.

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?

The description covers all necessary aspects: what the tool does, how to specify scaling, handling of different unit types, and behavior for missing quantities. It is complete enough for an agent to use the tool effectively without additional clarification.

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?

The description adds meaning to parameters: it explains the relationship between factor and from_servings/to_servings, and clarifies that ingredients are lines that may contain quantities. It also describes how lines without quantities are treated, providing more context than the schema descriptions.

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: 'Rescale a list of ingredient lines to a different number of servings'. It also specifies the input type (French ingredient list) and distinguishes it from sibling tools (search_recipes, get_recipe) by focusing on 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 provides explicit usage instructions: 'Give either factor directly, or from_servings and to_servings'. It also gives examples and notes about rounding and edge cases, but does not explicitly state when to prefer this tool over siblings, though the purpose is clear enough.

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-marmiton'

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