Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

create_households_recipe_actions_by_item_trigger_by_reci

Trigger a household recipe action (e.g., add to shopping list) based on a specific recipe and item.

Instructions

Trigger Action

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYes
recipe_slugYes
recipe_scaleNo
accept-languageNo
Behavior1/5

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects, required permissions, or whether the action is destructive. 'Trigger' implies an effect but remains opaque.

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?

While the description is short (2 words), it is underspecified rather than concise. It does not front-load useful information and fails to earn its place with meaningful content.

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 has no output schema, no annotations, and 4 parameters, the description is critically incomplete. It does not explain what 'trigger' means, the action's outcome, or how it fits with sibling tools.

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?

The schema has 4 parameters with 0% description coverage. The description adds no meaning to item_id, recipe_slug, recipe_scale, or accept-language beyond the schema's basic type/format info.

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 'Trigger Action' is a tautology that restates the generic term 'trigger' from the tool name without clarifying what the tool does. It fails to specify the resource, verb scope, or distinguish it from siblings.

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 guidance on when to use this tool versus alternatives like create_households_recipe_actions or other sibling tools. The description does not mention prerequisites, context, or exclusions.

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