list_households_mealplans_rulesRetrieve all household meal plan rules with pagination, sorting, and filtering options to manage meal planning efficiently.
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?
With no annotations provided, the description carries the full burden of behavioral disclosure, but 'Get All' discloses nothing about pagination, scoping to a household, authentication requirements, or response behavior. It is effectively a placeholder.
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 short, but this is under-specification rather than effective conciseness. It provides no-front-loaded meaningful information and every word is generic.
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?
Despite an output schema existing, the description is far too thin for a tool with 8 parameters and no sibling differentiation. It does not state which household's mealplan rules are listed, what pagination parameters mean, or any operational context needed to invoke it correctly.
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 does not explain any of the 8 parameters such as page, perPage, queryFilter, or orderBy. The description makes no attempt to compensate for the schema's lack of parameter documentation.
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 only 'Get All', which conveys a broad retrieval action but does not name the resource being retrieved or the operation's scope. It adds no meaningful information beyond what the tool name already implies, and it does not differentiate from the many other list_* siblings.
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 versus the related create/get/update/delete mealplans_rules sibling tools, nor any mention of context, prerequisites, or exclusions. An agent has nothing to route on.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.