Skip to main content
Glama
djwmarcx

Better Mealie MCP

by djwmarcx

list_households_shopping_items

Retrieve all shopping items for a household. Use pagination, filtering, and ordering to find specific items.

Instructions

Get All

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
orderByNo
perPageNo
queryFilterNo
orderDirectionNo
paginationSeedNo
accept-languageNo
orderByNullPositionNo

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, the description must disclose behavioral traits. 'Get All' provides no information on parameters, side effects, or results. It fails to indicate that this is a read-only operation with pagination and filtering.

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

Conciseness1/5

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

Although extremely short, the description is under-specified. It is not effective conciseness but rather a lack of necessary information.

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 8 parameters and an output schema, the description is severely incomplete. It does not mention pagination, sorting, or filtering capabilities, nor the purpose of the tool.

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% and the description adds no meaning to any of the 8 parameters. Parameters like 'page', 'orderBy', 'queryFilter' are completely 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?

The description 'Get All' is vague. It restates the verb but does not specify the resource (household shopping items) clearly. Among many list tools, it fails to distinguish itself.

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

Usage Guidelines2/5

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

No usage context is provided. The description does not indicate when to use this tool versus alternatives like list_households_shopping_lists or other list tools.

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