Skip to main content
Glama

WritersLogic business agents

recipe-scale

Recipe scaling with caller-declared non-linear rules — Scales up to 60 ingredient quantities by a servings ratio or a factor for an agent resizing a recipe or batch formula, applying per-ingredient rules the caller declares: linear (the labelled default), power exponent, fixed amounts, min/max clamps and rounding steps, with an optional display unit via unit-convert. Reports what rounding did (relative drift, rounds-to-zero). It does NOT know which in

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": "recipe-scale"
  }
}

Input Schema

NameRequiredDescriptionDefault
factorNoScale factor, instead of fromServings/toServings.
densityNoDefault density for displayUnit conversions that cross mass and volume.
toServingsNoServings wanted.
ingredientsYesIngredients with quantity, unit and optional scaling rule.
fromServingsNoServings the recipe is written for.
maxRelativeDriftNoFail an ingredient when rounding moves it by more than this fraction (0.1 = 10%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: 60-ingredient cap, no built-in culinary constants or density table, claimed-value mismatch fails, maxRelativeDrift failing, and rounding reporting. However, the closing sentence that would state the tool's known limitation is cut off mid-word, so the transparency story is incomplete.

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 scope and mechanism are front-loaded in one dense sentence with an em-dash, which works. But the definition ends in an uncompleted fragment ('It does NOT know which in'), which is visible sloppiness in an otherwise efficient 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?

There is no output schema and six parameters including nested density objects, so the description correctly spends space on failure modes and on what gets reported back (relative drift, rounds-to-zero). The truncated final clause is the only substantive gap; return shape is covered at a high level.

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 the baseline is 3. The description adds only modest cross-parameter meaning (display unit routed through unit-convert, linear being a labelled default rather than a culinary claim); most rule semantics are already spelled out in the schema itself.

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 (scales ingredient quantities) plus hard scope (up to 60 ingredients, servings ratio or factor) and the exact mechanism (per-ingredient caller-declared rules). An agent can distinguish it from unit-convert or a recipe matcher without opening the schema.

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?

Names the intended caller situation (an agent resizing a recipe or batch formula) and points at unit-convert for display units. A negative clause appears to be starting ('It does NOT know which in...') but is truncated, so the when-not-to-use half of the guidance never lands.

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