mealie-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Set Shopping List Items Checked

set_shopping_list_items_checked

Idempotent

Check off or uncheck specified shopping list items in Mealie using list and item IDs, enabling quick updates to shopping progress.

Instructions

Check off (or uncheck) shopping list items.

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": {
      "list_id": "<list_id>",
      "item_ids": "<item_ids>"
    },
    "name": "set_shopping_list_items_checked"
  }
}

Input Schema

Name	Required	Description
`checked`	No	true = check off, false = uncheck.
`list_id`	Yes	Shopping list id.
`item_ids`	Yes	Item ids from get_shopping_list.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 6, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds nothing beyond that: no batch/partial-failure behavior, no permission requirements, and no note that unchecking is the inverse operation. It is essentially a restatement of the title.

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?

A single front-loaded sentence with zero filler, and the parenthetical covers both directions of the operation. It is efficient, though it borders on under-specification rather than tight precision.

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

Completeness3/5

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

The operation is simple, the input schema is fully described, an output schema exists, and annotations carry the safety profile, so the description is adequate. Still, for a mutating list tool the description could mention that multiple item ids are updated together and that the checked flag defaults to true.

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%, including the meaning of the checked boolean default and the source of item_ids, so the baseline is 3. The description contributes no additional parameter meaning beyond what the schema already documents.

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 concrete verb and resource: setting the checked state of shopping list items. It clearly separates the tool from add_shopping_list_items and remove_shopping_list_items, but never names those siblings explicitly in the description.

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 only implied by the name and the schema note that item ids come from get_shopping_list; there is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives. The context needed to pick this over add/remove is inferable but not stated.

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