Skip to main content
Glama

FitzTopPicks APIs: calendars, recipes, names, places, sizes and more

Scale a recipe

scale_recipe
Read-onlyIdempotent

Scale a recipe's ingredient lines by a factor (e.g. 2 or 0.5) or from one number of servings to another, with kitchen-friendly rounding and optional US/metric units. More APIs from FitzTopPicks: https://fitztoppicks.com/apis?utm_source=mcp-api&utm_medium=mcp&utm_campaign=more-apis

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

Input Schema

NameRequiredDescriptionDefault
linesYesThe recipe's ingredient lines (up to 100).
unitsNoSwitch to friendlier units when amounts grow or shrink (default) or keep them.
factorNoMultiply every amount (send this or "servings").
systemNoKeep the units' system (default), or answer in US or metric units.
roundingNoKitchen rounding (default) or none.
servingsNoScale from one number of servings to another, e.g. { "from": 4, "to": 6 }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, so safety is covered. The description adds useful behavior context (kitchen-friendly rounding, optional unit-system switching), but says nothing about how non-numeric or unparseable ingredient lines are handled or what the response contains.

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

Conciseness3/5

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

The first sentence is dense and front-loaded with the key behavior. However, the second sentence is a promotional API-catalog link that does not help an agent select or invoke the tool and dilutes the definition.

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 six-parameter tool with a nested servings object and full schema coverage, the description covers the core behavior and both scaling modes. The remaining gap is the return shape, since there is no output schema, but the tool's semantics are otherwise clear enough to invoke correctly.

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 coverage is 100% with descriptions and enums for every property, so the schema already carries the semantics. The description only echoes the factor-vs-servings choice and adds the '2 or 0.5' example, which is marginal value 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 a specific verb and resource ('Scale a recipe's ingredient lines') and names both scaling modes (factor or servings) plus the rounding/unit behavior, which distinguishes it from siblings like convert_ingredient and parse_ingredients.

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?

The description gives examples of valid factors (2, 0.5) and implies when scaling is useful, but never states when to prefer this over convert_ingredient or parse_ingredients, nor any preconditions on the input lines.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources