Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

Bulk check shopping entries

bulk_check_shopping_entries
Idempotent

Checks or unchecks multiple shopping entries in one call, setting or clearing completed_at; missing or inaccessible IDs are skipped and the response returns the submitted IDs, checked value, and timestamp.

Instructions

Check or uncheck many shopping entries in one call. Checking sets completed_at to now, also on entries already checked; unchecking clears it. Ids that do not exist or are not visible to you are skipped, and the entries need not share a shopping list. Returns the ids and checked value sent plus a timestamp; it does not return the entries or say which ids were skipped. To change lists too, use bulk_update_shopping_entries; to change other fields, use update_shopping_entry.

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>",
      "checked": "<checked>"
    },
    "name": "bulk_check_shopping_entries"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesShopping entry IDs, from list_shopping_entries.
checkedYestrue checks, false unchecks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.4.4
    • addedInput schema / properties / checked / description
      Added value: +"true checks, false unchecks."
    • addedInput schema / properties / ids / description
      Added value: +"Shopping entry IDs, from list_shopping_entries."
  2. First observedv3.4.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations it discloses that checking overwrites completed_at with the current time even on already-checked entries, that nonexistent or invisible ids are silently skipped, and exactly what the response contains and omits. That is precisely the kind of consequence-level detail annotations cannot convey.

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?

Three compact sentences ordered by importance: action, side effects and skip semantics, then disambiguation. Every clause carries information and there is no filler.

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?

With only two required parameters, a documented schema, and no output schema, the definition covers behavior, edge cases, return shape, and alternatives. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3; the description adds real meaning by explaining what happens to ids that do not exist or are not visible and by clarifying that ids may span lists. It does not add format or ordering details for the ids array, keeping it short of a 5.

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 names a specific verb pair (check/uncheck), the resource (shopping entries), and the batch scope in the first sentence, so it is immediately distinguishable from update_shopping_entry and bulk_update_shopping_entries.

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 routes the agent explicitly to bulk_update_shopping_entries for list changes and update_shopping_entry for other fields, and notes entries need not share a list. It does not explicitly say when to prefer this over a single-entry update for one id, so the guidance is strong but not exhaustive.

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