Skip to main content
Glama

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

Write an ingredient line from fields

write_ingredient_line
Read-onlyIdempotent

Turn structured fields (amount, unit, item, prep, notes) into a natural recipe line ("1½ cups flour, sifted"), with plurals, fractions and 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": {
      "item": "<item>"
    },
    "name": "write_ingredient_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesThe ingredient.
prepNoPreparation: "finely chopped", "sifted", "drained and rinsed".
unitNoThe unit in any spelling /parse knows: cup, cups, tbsp, tablespoon, g, clove, can, large... (leave out for counted items).
notesNoAnything else, after a comma: "plus more to serve".
unitsNoshort (default) or long unit names.
amountNoThe amount: 1.5, "1 1/2", "1½" (leave out for "salt, to taste").
systemNokeep (default), us or metric.
optionalNoAdd "(optional)". Default false.
spellingNous (default: liters) or uk (litres) for long metric names.
amountMaxNoThe top of a range (2-3: amount=2, amountMax=3).
fractionsNounicode (default), ascii or decimal.
prepPositionNoauto (default), before or after the item.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, and the description's claims (pure deterministic formatting) are consistent with that. It adds some behavioral context by noting plural, fraction and unit-system handling, but says nothing about error behavior for unparseable amounts or what the returned value's shape is. No contradiction with annotations.

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 well front-loaded, with the example doing real work up front. The trailing 'More APIs from FitzTopPicks' link with UTM parameters is pure promotion that consumes roughly a third of the text without helping an agent call the tool correctly.

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 stateless 12-parameter formatter with full schema coverage and a clear annotation profile, the description supplies enough to call it correctly, and the inline example implicitly conveys the return value despite there being no output schema. The missing piece is explicit statement of the response type and failure mode, which is minor given the schema's completeness.

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 every one of the 12 parameters is already documented in the schema, including enum values and defaults. The description only names 5 of the 12 fields (amount, unit, item, prep, notes) and adds no syntax or interaction detail beyond what the schema provides. Baseline 3 applies.

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 ('Turn structured fields ... into a natural recipe line') and reinforces it with a concrete example output ('1½ cups flour, sifted') plus the formatting concerns it handles (plurals, fractions, US/metric units). It is clearly distinguishable from a unit-conversion sibling like convert_ingredient, though it never names an alternative explicitly.

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 usage is implied by the task itself: given parsed ingredient components, produce a rendered line. There is no explicit statement of when to prefer this over convert_ingredient, no prerequisites, and no exclusions or edge-case guidance (for example what to do when formatting is already natural).

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