list_zonesRetrieve a list of all zones in your home organized by hierarchy (Home, Floors, Rooms) including zone ID, name, parent zone, and icon.
List all zones (rooms/areas) in the home with their hierarchy. Returns zone ID, name, parent zone, and icon. Zones are organized in a tree: Home → Floors → Rooms.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a safe read operation (readOnlyHint=true, destructiveHint=false). The description adds value by disclosing what data is returned (zone ID, name, parent zone, icon) and the tree structure (Home → Floors → Rooms), which is useful contextual behavior beyond the annotations.
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 two sentences, front-loaded with the core purpose, and every word earns its place. It efficiently conveys the action, resource, return fields, and hierarchy without any redundancy or fluff.
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 lacking an output schema, the description specifies the return fields and hierarchy, which is sufficient for a simple list tool with no parameters. The agent can predict exactly what to expect, making the description complete in context.
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 tool has zero parameters, and the input schema is empty with 100% schema coverage. Per baseline rules, a score of 4 is appropriate since there is no parameter information needed; the description appropriately does not try to invent parameter details.
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 uses a specific verb ('list') and resource ('zones') while clarifying that zones are rooms/areas in the home. It further specifies the hierarchical structure and return fields, making its purpose unmistakable and distinct from sibling tools like list_devices or list_apps.
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?
The description clearly implies when to use this tool (when you need zone information like rooms/areas and their hierarchy), but it does not explicitly mention alternatives or exclusions. The context is clear enough for the agent to infer usage without needing an explicit 'use this instead of list_devices' statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.