list_households_cookbooksRetrieve a paginated list of all household cookbooks from Mealie, with options to filter, sort, and paginate results.
Get All
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | ||
| paginationSeed | No | ||
| accept-language | No | ||
| orderByNullPosition | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.20.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided and the description says nothing about side effects, read-only behavior, pagination behavior, permissions, or response characteristics. The full burden of behavioral disclosure falls on the description, and it discloses nothing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two words are short, but this is under-specification rather than efficient conciseness. The description omits the resource, purpose, parameter context, and usage guidance, so it does not earn its place as a useful definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Although an output schema exists, the description still fails to state what is being listed, how to paginate or filter, or what constraints apply. For an 8-parameter list tool amid many similar list tools, this is severely incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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. An agent gets only raw parameter names like page, orderBy, perPage, queryFilter, paginationSeed, and accept-language, with no explanation of format, defaults, or semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description is simply 'Get All'—it does not name cookbooks, households, or any concrete resource. It only restates the 'list' nature implied by the tool name and title, so an agent cannot determine what is actually being retrieved or how this tool differs from the many sibling list_* tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance about when to use this tool, what scenarios it fits, or how it differs from similar list tools. With over a hundred sibling tools and no annotations, the description provides zero routing or selection information.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.