Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

create_households_mealplans

Creates a household meal plan entry for a specific date and meal type, optionally linked to a recipe or with custom text.

Instructions

Create One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
textNo
recipeIdNo
entryTypeNo
accept-languageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations exist, and the description fails to disclose any behavioral traits like side effects, required permissions, or return format. The phrase 'Create One' implies a single creation but no further details.

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

Conciseness2/5

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

Extremely brief (two words), but conciseness should not sacrifice informativeness. The description is under-specified, making it unhelpful despite being short.

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

Completeness1/5

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

With 5 parameters (1 required) and no schema descriptions, the description fails to provide necessary context. An output schema exists, but the description still lacks sufficient information for correct tool invocation.

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% and the description adds no meaning to the five parameters (date, text, recipeId, entryType, accept-language). Parameters remain unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Create One' is a tautology of the tool name 'create_households_mealplans'. It does not specify what is being created (e.g., a meal plan entry) and offers no differentiation from sibling tools like create_households_mealplans_random.

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

Usage Guidelines1/5

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

No usage context provided. Does not indicate when to use this tool vs alternatives such as create_households_mealplans_rules or create_households_mealplans_random.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/djwmarcx/better-mealie-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server