mealie-agent-mcp

Overview Schema Source Related Servers Discussions Admin

Create Shopping List

create_shopping_list

Create a new, empty shopping list in Mealie by supplying a list name, enabling organized item tracking for meals or errands.

Instructions

Create a new, empty 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": {
      "name": "<name>"
    },
    "name": "create_shopping_list"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name of the new 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

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered externally. The description adds the useful fact that the resulting list is empty, but says nothing about name uniqueness, whether duplicates are rejected, or what the response contains. Modest added value beyond annotations.

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 short sentence with zero redundancy, front-loaded with the verb. It is efficient but so terse that it leaves almost every question an agent might have unanswered.

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 tool is simple (one required string) and has an output schema, so the description does not need to explain return values. However, it omits the one behavioral fact that matters for a create operation - what happens when a list with that name already exists - leaving a real gap for a mutation tool.

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% with a single required string parameter already documented as 'Name of the new list.' The description adds no format, length, or uniqueness constraints beyond that, so baseline 3 applies.

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 specific verb and resource (create a shopping list) and adds a meaningful qualifier, 'empty', which implicitly separates it from add_shopping_list_items and add_recipe_to_shopping_list. It does not name any sibling explicitly, so it stops short of a 5.

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?

There is no explicit when-to-use guidance, no mention of prerequisites (e.g. that a list must exist before items can be added), and no statement about which sibling to pick instead. The only signal is the word 'empty', which a careful reader can infer means 'use this before populating'.

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