list_households_shopping_listsRetrieve all shopping lists for your household with support for pagination, filtering, and sorting to quickly access the lists you need.
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, and 'Get All' provides none. It does not state that this is a read-only list operation, whether pagination limits the result, or how the 8 parameters affect behavior. An agent cannot anticipate side effects or output characteristics.
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 and front-loaded, but this is under-specification rather than effective conciseness. 'Get All' does not earn its place because it adds almost no discriminative or operational information.
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?
For an endpoint with 8 optional parameters, no annotations, a large sibling tool set, and no behavioral or parameter context, the description is inadequate. Although an output schema exists, the agent still lacks enough information to select the tool confidently or configure its parameters 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 compensate. Parameters such as page, perPage, queryFilter, orderBy, and paginationSeed are left entirely unexplained. 'Get All' even creates ambiguity about whether pagination applies at all.
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 essentially restates the verb already present in the tool name and title ('List Households Shopping Lists'). It does not clearly name the resource or scope in the description itself, and it does not distinguish itself from siblings such as get_households_shopping_lists_by_item or list_households_shopping_items.
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 on when to use this tool versus related list/get/single-item tools. 'Get All' only weakly implies retrieving all shopping lists, but no context, exclusions, or alternatives are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.