Mealie MCP

add_shopping_item

Add a single item to a shopping list. Specify the list, note, and optionally food, quantity, and unit.

Instructions

Add a single item to a shopping list.

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>",
      "note": "<note>"
    },
    "name": "add_shopping_item"
  }
}

Input Schema

Name	Required	Description	Default
`food`	No
`note`	Yes
`unit`	No
`list_id`	Yes
`quantity`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 7, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It only states the basic action; does not disclose error behavior (e.g., if list_id does not exist), idempotency, or what the 'note' field is for. Lacks context beyond the minimal action.

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?

Single sentence is concise but overly terse, omitting essential parameter explanations and usage context. Adequate for a very simple tool but not well-structured for an agent to understand all input fields.

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?

Output schema exists (suggesting return of created item), but description still lacks context on prerequisites (e.g., list existence, authentication), side effects (e.g., appending to list), and edge cases. Incomplete for effective tool selection.

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 coverage is 0%; description adds no meaning to any of the 5 parameters. Does not explain that list_id identifies the target list, note is required (and its purpose), or defaults for food, unit, quantity.

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?

Description clearly states verb 'Add', resource 'item', and target 'shopping list'. Distinct from siblings like add_recipe_to_shopping_list (which adds multiple items from a recipe) and check_shopping_item (which marks an item as checked).

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 guidance on when to use this tool vs alternatives. Does not mention that for adding items from a recipe, one should use add_recipe_to_shopping_list instead, or that for checking items, check_shopping_item is appropriate.

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