Skip to main content
Glama

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

Merge recipes into one shopping list

merge_shopping_lists
Read-onlyIdempotent

Merge the ingredient lists of up to 20 recipes into one shopping list grouped by grocery aisle, adding up the same items (each list can be scaled), with pantry staples kept apart by default. 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": {
      "lists": "<lists>"
    },
    "name": "merge_shopping_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
listsYesThe recipes: [{ "name": "Tacos", "lines": ["1 lb ground beef", ...] }].
systemNoUnits of the merged list (default us).
staplesNoKeep pantry staples (salt, oil...) in their own group (default) or in the list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/ idempotent / non-destructive / closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: aisle-based grouping, automatic summation of matching items, per-list scaling, and the default pantry-staples split. It does not describe the shape of the returned list, which is the main remaining gap.

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

Conciseness4/5

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

The functional content is front-loaded into one dense sentence with no filler, and the cap, grouping, scaling, and staples behavior all earn their place. The trailing promotional URL for 'More APIs from FitzTopPicks' with UTM parameters is pure noise for tool selection and slightly dilutes an otherwise tight 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 three-parameter, enum-rich, single-purpose transformation tool with full schema coverage, the description covers scope, aggregation behavior, scaling, and output grouping. The only missing piece is what the returned merged list looks like (no output schema exists), which would help an agent plan follow-up steps.

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 schema already documents 'lists', 'factor', 'system', and 'staples' with defaults and enums. The description reinforces a few of these (scaling, staples default, 20-item cap) but adds no syntax or format detail the schema lacks. Baseline 3 applies when the schema does the heavy lifting.

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?

The description names a specific verb and resource ('Merge the ingredient lists of up to 20 recipes into one shopping list') and adds concrete outcome details: grouping by grocery aisle, summing duplicate items, per-list scaling, and staples kept apart. An agent can distinguish this from single-list tools such as scale_recipe or parse_ingredients, though no sibling is named 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?

Usage is implied rather than stated: the description makes clear this is the tool for combining multiple recipe ingredient lists, and the 'up to 20' ceiling plus 'staples kept apart by default' hints at scope boundaries. There is no explicit when-to-use/when-not guidance, no named alternative for single-recipe scaling, and no stated prerequisites.

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