netatmo_list_homesList homes in a Netatmo account that have energy devices, including room and device counts and whether boiler history is available.
List the homes in the Netatmo account that have Energy devices (thermostats, radiator valves), with room and device counts and whether boiler history is available.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| homes | Yes |
Changes observed during successful MCP inspections.
v0.3.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds the filtering behavior (homes without Energy devices are excluded), which is genuine value, but the rest of the sentence largely restates what an output schema would carry.
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?
A single tight sentence with the resource front-loaded and no filler. Slightly dense with multiple clauses (scope, device types, counts, boiler history) but every element informs the caller.
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 zero params, an output schema covering return values, and annotations covering safety, the description only needs to establish scope — which it does. The one remaining gap is routing versus netatmo_get_home, which is not addressed.
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?
Zero parameters, so the baseline of 4 applies; there is nothing parameter-related the description could or should explain.
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?
Specific verb+resource (list homes) plus a meaningful scope qualifier (only homes with Energy devices) and a preview of the returned fields (room/device counts, boiler history). It does not, however, differentiate from the close sibling netatmo_get_home, so an agent could hesitate between the two.
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?
Usage is only implied: the filter on Energy devices hints that this is the entry point for heating workflows, but there is no explicit 'use this before X' instruction and no mention of netatmo_get_home or netatmo_list_devices as alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.