Skip to main content
Glama
Better Mealie MCP

Better Mealie MCP

List Households Mealplans

list_households_mealplans

Retrieve household meal plans with pagination, date-range filtering, ordering, and optional week entries to review scheduled meals.

Instructions

Get All

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_households_mealplans"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
orderByNo
perPageNo
end_dateNo
start_dateNo
queryFilterNo
orderDirectionNo
paginationSeedNo
accept-languageNo
orderByNullPositionNo
include_week_entriesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.30.0
    • addedInput schema / properties / include_week_entries
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv3.20.1

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether results are paginated, sorted by default, scoped to the caller's household, or affected by the date-range parameters.

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?

It is short, but shortness here is under-specification rather than conciseness: two words with no front-loaded scope or key facts. A single useful clause about what is returned and how filters behave would have earned the length.

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?

An 11-parameter list endpoint with no annotations and zero schema coverage needs a substantive description; this has none. The presence of an output schema covers return values, but nothing else about correct invocation is addressed.

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% across 11 parameters, and the description adds no meaning at all. Non-obvious parameters like paginationSeed, queryFilter, orderByNullPosition, accept-language, and include_week_entries are left entirely unexplained.

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

Purpose2/5

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

"Get All" only restates the verb implied by the tool name and adds no resource detail, scope, or filtering semantics. It does at least imply an unfiltered listing rather than a single-item fetch, but an agent learns nothing beyond what "list_households_mealplans" already conveys.

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 when-to-use guidance and no mention of alternatives, despite many closely related siblings such as list_households_mealplans_today, get_households_mealplans_by_item, and list_households_mealplans_rules. Nothing tells the agent which of these to pick.

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