Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

Update Households Mealplans Rules By Item

update_households_mealplans_rules_by_item

Modify an existing household meal-plan rule for a specific item, changing its day, meal type, or query filters as needed.

Instructions

Update One

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": "update_households_mealplans_rules_by_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoThe day a meal plan rule applies to, or the weekday of the meal plan entry rules are looked up for. On a rule, `unset` means the rule applies to all days. When looking up rules for an entry, `unset` means the entry isn't on a specific weekday (e.g. it spans a week), so only rules that apply to all days match it.
item_idYes
entryTypeNo
accept-languageNo
queryFilterStringNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.30.0
    • addedInput schema / properties / day / description
      Added value: +"The day a meal plan rule applies to, or the weekday of the meal plan entry rules are looked up for.\n\nOn a rule, `unset` means the rule applies to all days. When looking up rules for an entry, `unset`\nmeans the entry isn't on a specific weekday (e.g. it spans a week), so only rules that apply to all\ndays match it."
  2. First observedv3.20.1

TDQS

D1.1/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full disclosure burden and delivers nothing. It does not state that this is a mutation, what permissions are required, whether omitted fields are preserved, or how partial updates behave.

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?

Two words are technically concise, but this is under-specification rather than economy. There is no front-loaded statement of action or scope; the text conveys nothing an agent can act on.

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?

For a mutation tool with five parameters, only one required, no annotations, and 20% schema coverage, the description omits everything an agent needs to invoke it safely. The presence of an output schema covers return values only, not the massive gaps on inputs and effects.

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?

With five parameters and only 20% schema description coverage, the description must compensate and does not. It adds no meaning for item_id, entryType, accept-language, or queryFilterString, leaving the required item_id and the query filter semantics entirely 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?

"Update One" names no verb-specific resource and is effectively a tautology of the title. It gives no indication that this mutates a meal-plan rule identified by item_id, and nothing distinguishes it from sibling updaters like update_households_mealplans_by_item or update_households_mealplans_rules_by_item's delete/get counterparts.

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?

There is no when-to-use guidance, no prerequisite, and no mention of the alternative tools such as create_households_mealplans_rules or get_households_mealplans_rules_by_item. An agent has no basis for choosing this tool over its many siblings.

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

Deploy Server

Other Tools