Skip to main content
Glama
mcp-ptitchef

mcp-ptitchef

Rescale an ingredient list

scale_ingredients
Read-onlyIdempotent

Rescale French ingredient lines to a different serving count by applying a factor or computing one from source and target servings, rounding quantities readably and flagging lines without amounts.

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 pasted in by hand. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ingredients": "<ingredients>"
    },
    "name": "scale_ingredients"
  }
}

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.0
    • removedOutput schema / properties / ingredients / items / properties / amount / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ingredients / items / properties / amount / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ingredients / items / properties / amount_max / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ingredients / items / properties / amount_max / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ingredients / items / properties / unit / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ingredients / items / properties / unit / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv1.0.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, idempotent, not open-world); the description adds substantial behavioral detail annotations cannot express — rounding rules for grams/millilitres, the half-vs-whole logic for countables with concrete examples, handling of approximate measures, and that quantity-less lines are returned untouched and flagged. It also confirms the French-language constraint and the no-network behavior.

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

Conciseness4/5

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

Front-loaded with the core action and input-mode choice, with detail layered afterward. The rounding sentence is long and example-heavy, but each rule carries real information an agent needs to predict output.

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?

An output schema exists so return shape need not be explained, and the description still notes that unquantified lines are flagged. Given four parameters, a rich rounding policy, and a language restriction, the description covers everything needed to call it correctly.

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, but the description adds genuine meaning: the mutually exclusive factor vs. from/to pair and how the factor is derived, plus how numeral-less lines like 'un bouchon de rhum' are interpreted. It does not clarify bounds (max 100 factor, max 100 lines) that the schema already handles.

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 a specific verb and resource ('Rescale a list of ingredient lines to a different number of servings') plus a clear scope constraint ('without contacting any website'). It is unmistakable against the sibling tools, which are all recipe lookup/search operations, not arithmetic transforms.

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 tells the agent how to choose the input mode ('Give either factor directly, or from_servings and to_servings and the factor is computed') and when to prefer this tool over the default behavior ('Prefer this over doing the arithmetic yourself'). Scope is also bounded ('any French ingredient list, whatever its source').

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