Skip to main content
Glama

weReci

by xyz.wereci
OverviewDiscussionsAdmin

Add to your shopping list

add_to_shopping_list
Idempotent

Put things ON the user's own shopping list (List It) — the running list they carry in the app. Call it ONLY when the user explicitly asks to add, save, or collect for later ("put those on my list", "save the ingredients for Sunday", "also add paper towels") — never speculatively, and never as a follow-up they didn't ask for. Pass recipes by id in recipe_ids (their ingredient lines go on), and/or plain one-off items in items ("paper towels", "2 lemons") — at least one of the two. This tool only COLLECTS: to propose a consolidated list or hand one off for shopping (cart, email), use build_shopping_list instead. Re-adding a recipe replaces its lines (safe to repeat). Pass pantry staples the user keeps in 'exclude' and mention what you skipped. recipe_ids MUST be copied exactly from search_recipes hits, the retrieved set, or list_conceits members — never invented. share decides WHERE the lines go: the user's shared list (visible to Home Assistant and a cookbook partner) or the list on their phone; leave it out unless they said.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsNoOne-off things the user named that aren't a recipe — plain lines as they said them, e.g. "paper towels", "2 lemons". Omit when only adding recipes.
shareNotrue: put the lines on the user's SHARED list — the one Home Assistant, connected assistants and a cookbook partner can see and tick; if the user isn't on it yet this also joins them to it, and their app then shows that list until they stop sharing. false: keep them private on the user's phone. Omit unless the user said which — the default is their own setting.
excludeNoIngredients to leave off — pantry staples the user keeps, or items they said to drop. Plain names, e.g. "soy sauce". Applies to recipe lines only, never to explicit items.
recipe_idsNoUp to 8 recipe point ids, exactly as returned by your tools. Omit when only adding one-off items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, idempotent=true, destructive=false), it discloses that re-adding a recipe replaces its lines, that recipe_ids must come from specific tool results and never be invented, and that share controls whether lines land on the shared or phone list with a joining side effect. These are meaningful behavioral details that the annotations alone do not provide.

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

Conciseness5/5

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

The description is dense but every sentence carries operational guidance: call conditions, parameter usage, alternatives, idempotency, and provenance. The core action and the most important guardrail are front-loaded before details.

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

Completeness5/5

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

For a 4-parameter mutation tool with no output schema, the description covers selection, invocation, side effects, and the two key sibling behaviors. It also provides explicit no-go cases and exact recipe-id provenance, so an agent has what it needs to invoke safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema descriptions cover 100% of parameters, the description adds cross-parameter constraints such as "at least one of the two", explains that recipe ingredient lines go onto the list, and instructs the agent to pass exclusions and "mention what you skipped". It also adds provenance requirements for recipe_ids not present in 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?

The description opens with a specific action and resource: "Put things ON the user's own shopping list (List It)", and it clarifies the collection-only role. It also distinguishes itself from build_shopping_list by saying that consolidated/hand-off flows belong there, so an agent can tell them apart without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit call conditions: only when the user asks to "add, save, or collect for later", and explicit prohibitions: "never speculatively, and never as a follow-up they didn't ask for". It names build_shopping_list as the alternative for proposing or handing off a list, and sets the at-least-one-parameter and share-omission rules.

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

All weReci toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources