Mealie MCP

check_shopping_item

Mark shopping list items as checked or unchecked to track completion status.

Instructions

Mark a shopping list item as checked or unchecked.

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": {
      "item_id": "<item_id>"
    },
    "name": "check_shopping_item"
  }
}

Input Schema

Name	Required	Description	Default
`checked`	No
`item_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The description only states the basic effect (mark as checked/unchecked). With no annotations provided, the description carries the full burden for behavioral disclosure. It does not mention the default value of 'checked' (true), whether it toggles or sets explicitly, or any consequences like notifications or list updates.

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

Conciseness3/5

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

The description is extremely concise (one sentence). While brevity is good, it sacrifices important details like parameter semantics and behavioral nuances. It could be restructured to include param info without losing conciseness.

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

Completeness2/5

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

Given the tool's simplicity (2 params, no nested objects) and the presence of an output schema (not shown), the description could still provide more context about return values, side effects, or prerequisites. It is incomplete for an agent to use confidently.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain any parameters. It does not clarify the role of 'checked' or 'item_id' beyond what the schema (names and types) already provides. A minimal description like 'item_id: the ID of the item to update; checked: whether to mark it as checked (default true)' would add value.

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 clearly states the action (mark as checked/unchecked) and the resource (shopping list item), making the purpose immediately understandable. However, it does not explicitly distinguish from sibling tools like add_shopping_item or delete_shopping_item, but the verb+resource combination is specific enough.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. While the action is obvious, there is no mention of prerequisites, side effects, or conditions that would help an agent decide when to call this vs other shopping list item tools.

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