Skip to main content
Glama
Ingredient Convert MCP

Ingredient Convert MCP

scale_recipe

Read-onlyIdempotent

Scale recipe ingredient amounts by any factor—double, halve, or use 1.5x—and return friendly fractions like 1 1/2 cups for any unit or count.

Instructions

Scale recipe ingredient amounts by a factor (double, halve, 1.5x...). Output in friendly fractions like 1 1/2 cups. Any unit can be scaled (cups, tbsp, grams, cloves, cans); a line without a unit is a count, e.g. 2 eggs.

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": {
      "items": "<items>",
      "factor": "<factor>"
    },
    "name": "scale_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesRecipe lines to scale
factorYesScale factor, e.g. 2 to double, 0.5 to halve

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real value beyond them by disclosing the output shape ('friendly fractions like 1 1/2 cups') and the unit/count semantics, which matter because no output schema exists.

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?

Three short sentences, each doing distinct work: purpose, output format, and unit/count handling. The core purpose is front-loaded and there is 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?

For a simple, closed-world pure-computation tool with two fully described parameters, the definition is nearly complete, and it compensates for the absent output schema by describing the fraction-style return format. Only edge-case behavior, such as how awkward non-nice fractions are rounded, is left unstated.

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 both parameters are already documented in the schema, including the 'omit unit for a count' rule and factor examples. The description largely restates those same semantics, so the baseline of 3 applies with no meaningful additional parameter detail.

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 ('Scale recipe ingredient amounts by a factor') with concrete examples of factors, which is enough for an agent to distinguish it from conversion siblings like convert_ingredient. It stops short of naming an alternative tool or explicitly contrasting scaling with conversion, so it is clear but not fully differentiated.

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 the phrasing 'scale by a factor' and the examples (double, halve, 1.5x), so an agent can infer this is for multiplying an existing recipe rather than converting units. However, there is no explicit when-to-use / when-not-to-use guidance and no named alternative for unit conversion tasks.

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