Skip to main content
Glama

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

Convert ingredient units

convert_ingredient
Read-onlyIdempotent

Convert an ingredient amount between US and metric units, or to one unit (g, ml, cup, oz, tbsp...). Volume to weight only for items with a known density (e.g. 250 g sugar to cups). Send one "line", up to 100 "lines", or "amount" + "unit" (+ "item" for volume <-> weight), and "to". 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": {
      "to": "<to>"
    },
    "name": "convert_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes"metric", "us" or a unit: tsp, tbsp, cup, fl oz, pint, quart, gallon, ml, l, oz, lb, g, kg.
itemNoThe ingredient (needed for volume <-> weight), e.g. sugar.
lineNoOne ingredient line, e.g. "1 1/2 cups flour".
unitNoThe amount's unit, e.g. g, cup, oz.
linesNoUp to 100 ingredient lines.
amountNoAn amount (with "unit"), e.g. 250 or "1 1/2".
preferNoKeep the kind of unit (same, default), or prefer weight or volume.
spoonsNoKeep teaspoons and tablespoons as they are (default) or convert them too.
roundingNoRound to kitchen-friendly amounts (default) or not at all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description's job is to add constraints — and it does: the density requirement for volume/weight conversion and the 100-line batch ceiling. It stops short of saying what happens when density is unknown or how a failed conversion is signaled.

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 three sentences are tight and front-loaded with the core purpose before the input modes. The final sentence ("More APIs from FitzTopPicks: https://...?utm_source=mcp-api...") is pure marketing with tracking parameters and earns no place in a tool definition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters and no output schema, the definition covers inputs well but says nothing about the return value — an agent cannot tell whether it gets a formatted string, a number, or a per-line array for batch calls. That gap keeps it at minimum-viable for a tool of this complexity.

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 baseline is 3, but the description adds real meaning the schema does not: that line / lines / amount+unit are alternative mutually exclusive input pathways rather than combinable fields, and that item is only needed for the volume<->weight case despite being optional in the schema.

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?

"Convert an ingredient amount between US and metric units, or to one unit (g, ml, cup, oz, tbsp...)" gives a specific verb and resource plus the conversion directions supported. It does not name a sibling such as parse_ingredients or scale_recipe to delineate boundaries, so it lands at 4 rather than 5.

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?

It specifies the valid input combinations ("Send one 'line', up to 100 'lines', or 'amount' + 'unit' (+ 'item' for volume <-> weight)") and the condition under which weight<->volume works (known density, e.g. sugar). That is genuinely actionable context, but there is no guidance on when to prefer this tool over parse_ingredients or scale_recipe.

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