list_admin_householdsRetrieve a paginated list of all households with support for filtering, ordering, and pagination to locate and manage household records.
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' reveals nothing: it doesn't state that this is a read operation scoped to all households in the system, whether pagination applies, or what permissions are required. This is effectively a placeholder rather than a behavioral disclosure.
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?
'Get All' (two words) is under-specification, not conciseness — the opposite of a well-structured description. Even a single sentence describing scope or usage would add value and still be concise.
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 8-parameter admin-scoped listing tool in a large family of list tools, the description omits scope, access requirements, filtering behavior, and pagination semantics. Although an output schema exists so return values don't need explanation, an agent still lacks everything needed to select and invoke the tool 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%, so none of the 8 parameters have documentation in the schema, and the description names none of them either. Ambiguous parameters like queryFilter and paginationSeed are left completely unexplained, leaving an agent unable to construct a call beyond invoking defaults.
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 'Get All,' which merely restates the listing action implied by the name and title without specifying what is being listed, the administrative scope, or pagination semantics. The actual meaning is carried entirely by the tool name and title, not the description, and it does nothing to distinguish this from siblings like list_admin_users, list_households_self, or list_groups_households.
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 whatsoever about when to use this tool versus alternatives. The description offers no context about admin authorization requirements, no comparison to get_admin_households_by_item for single-item lookups, and no distinction from the many other list_* sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.