Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

Bulk update shopping entries

bulk_update_shopping_entries
Idempotent

Update multiple shopping entries in one call: check or uncheck items and add, remove, replace, or clear their shopping lists while skipping invalid or inaccessible entry IDs.

Instructions

Update many shopping entries in one call. Required: ids (entry ids; ids that do not exist or are not visible to you are skipped). Give checked, a list change, or both. checked: true checks every entry and sets completed_at to now, also on entries already checked; without checked, checked and completed_at stay as they are. List changes do not update the entries' updated_at. List changes: shopping_lists_add and shopping_lists_remove (may be combined), shopping_lists_set (replaces the lists; must not be empty) or shopping_lists_remove_all: true (takes every list off). set and remove_all must be used alone. Empty arrays and shopping_lists_remove_all: false count as no change and are not sent. An id may not appear in both shopping_lists_add and shopping_lists_remove. Every list id is checked against list_shopping_lists first; unknown or repeated ids are rejected and nothing is written.

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": {
      "ids": "<ids>"
    },
    "name": "bulk_update_shopping_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesShopping entry IDs, from list_shopping_entries.
checkedNotrue checks, false unchecks. Omitted keeps each value.
shopping_lists_addNoShopping list IDs to add, from list_shopping_lists.
shopping_lists_setNoReplaces all lists with these IDs. Must not be empty.
shopping_lists_removeNoShopping list IDs to remove.
shopping_lists_remove_allNotrue takes every list off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv3.4.4
    • addedInput schema / properties / checked / description
      Added value: +"true checks, false unchecks. Omitted keeps each value."
    • addedInput schema / properties / ids / description
      Added value: +"Shopping entry IDs, from list_shopping_entries."
    • addedInput schema / properties / shopping_lists_add / description
      Added value: +"Shopping list IDs to add, from list_shopping_lists."
    • addedInput schema / properties / shopping_lists_remove / description
      Added value: +"Shopping list IDs to remove."
    • addedInput schema / properties / shopping_lists_remove_all / description
      Added value: +"true takes every list off."
    • addedInput schema / properties / shopping_lists_set / description
      Added value: +"Replaces all lists with these IDs. Must not be empty."
  2. First observedv3.4.0

TDQS

A4.5/5.0
Behavior5/5

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

Far beyond the annotations, it discloses skip behavior for unknown ids, that checked:true stamps completed_at to now even on already-checked entries, that list changes leave updated_at untouched, that empty arrays / remove_all:false are silently dropped, and that invalid list ids cause "nothing is written" (atomic validation). The only nuance is that re-stamping completed_at on repeat calls sits slightly in tension with idempotentHint=true, though the resulting checked state is stable.

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?

Front-loaded with purpose and the required parameter, and every clause carries a distinct rule with no filler. It is a dense single paragraph of interleaved rules, though, so a reader must parse carefully rather than skim.

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 6-parameter mutation tool with no output schema, it covers composition rules, validation order, atomicity, and field side effects well. The main omission is what the call returns (affected vs skipped ids, resulting entries), which matters since no output schema exists to fill that gap.

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 already 100%, so the baseline is 3, but the description adds genuine cross-parameter meaning the schema cannot express: mutual exclusion of add/remove ids, set and remove_all needing to be alone, set replacing rather than appending, and empty-array no-op semantics. It stops short of documenting id formats beyond naming list_shopping_lists/list_shopping_entries as sources, but that is already 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?

"Update many shopping entries in one call" gives a specific verb (update), resource (shopping entries) and scope (many/bulk), which implicitly separates it from the single-entry update_shopping_entry and from bulk_check_shopping_entries. The required `ids` clause immediately confirms the bulk, id-addressable nature.

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 states clearly what must be supplied ("Give checked, a list change, or both") and the exclusivity rules ("set and remove_all must be used alone"), which is real when-to-use guidance for composing a call. It does not explicitly route the agent to update_shopping_entry for a single entry or to bulk_check_shopping_entries for check-only bulk work, so alternatives are left implicit.

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