Fetch a paginated list of households from the Mealie instance, with support for filtering, sorting, and ordering to locate specific household records.
Get All Households [GET /api/groups/households]
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| orderBy | No | ||
| perPage | No | ||
| queryFilter | No | ||
| orderDirection | No | desc | |
| paginationSeed | No | ||
| orderByNullPosition | No |
Changes observed during successful MCP inspections.
v0.2.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description fails to disclose any behavioral traits such as whether the operation is read-only, requires authentication, returns paginated results, or has any side effects. The description is completely silent on behavior.
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?
The description is extremely short but lacks essential details. It is front-loaded with the tool title and route, but does not include any explanatory text. Conciseness is not earned here as the content is insufficient for understanding.
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?
Given the tool's complexity (7 parameters, many siblings, no output schema), the description is severely incomplete. It does not explain the return format, pagination behavior, or how this tool relates to similar ones, making it nearly useless for an AI agent.
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?
The input schema contains seven parameters (page, orderBy, perPage, queryFilter, orderDirection, paginationSeed, orderByNullPosition), all with 0% schema description coverage. The description provides no information about these parameters, leaving the AI agent to guess their purpose and usage.
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 'Get All Households' is a verb+resource combination, but it's vague and does not differentiate from sibling tools like 'get_one_household', 'get_household', or 'explore_households_get_all'. No scope or context is provided, making the purpose ambiguous.
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?
No guidance is provided on when to use this tool versus alternatives. For example, it does not specify that this tool lists all households with pagination and filtering, while 'get_one_household' retrieves a specific household. The description lacks any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.