Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

update_households_cookbooks_by_item

Update a household's cookbook item by its ID, modifying the name, description, position, or visibility to organize recipes.

Instructions

Update One

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
slugNo
publicNo
item_idYes
positionNo
descriptionNo
accept-languageNo
queryFilterStringNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. 'Update One' does not indicate whether the update is full or partial, required permissions, side effects, or response structure. This is a critical gap for a mutation tool.

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?

The description is extremely concise (2 words) but sacrifices all meaningful content. While brevity is valued, this level of terseness undermines usability and does not earn its place.

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?

Given the tool's complexity (8 parameters, many siblings, no annotations, and an output schema that is not described), the description is severely incomplete. It fails to cover purpose, usage, parameters, behavior, or output.

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%, meaning the input schema provides no descriptions for any of the 8 parameters. The description adds no parameter explanations, leaving the agent with only parameter names which are insufficient for correct usage.

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?

The description 'Update One' is a tautology that adds no information beyond the tool name. It fails to specify what resource is being updated, making it impossible for an agent to determine the tool's purpose without relying solely on the name.

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?

The description provides no guidance on when to use this tool or when to prefer alternatives. Given numerous sibling tools for updating different entities (e.g., update_households_cookbooks, update_households_shopping_items_by_item), the lack of usage context leaves the agent uncertain about selection.

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