Retrieve a complete overview of a heating device in one call, including all modules, parameters, and current values. Use it to assess the full system state quickly.
Get a complete overview of a device: all modules with all their parameters and current values in a single call. Useful for getting a full picture of the heating system state.
| Name | Required | Description | Default |
|---|---|---|---|
| deviceId | Yes | Device ID (from wem_get_devices) |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It does disclose the key behavior that this is an aggregate single-call read returning every module's parameters and current values, which hints at a large response. It omits whether the payload is truncated/paginated, permission requirements, and cost of a full sweep.
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?
Two tight sentences, front-loaded with the core capability and the "single call" qualifier before the usage note. The second sentence is mildly redundant but does add decision context rather than padding.
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?
With one required parameter, no annotations, and no output schema, the description usefully compensates by describing what comes back (all modules, all parameters, current values). It is nearly complete for a simple read tool; only pagination/size expectations and a sibling comparison are missing.
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 coverage is 100%, and the schema already documents that deviceId comes from wem_get_devices, so the schema does the heavy lifting. The description adds no further meaning about the parameter, which is the expected baseline for fully documented single-parameter tools.
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?
States a specific verb and resource (get an overview of a device) and defines scope precisely: all modules with all parameters and current values in one call. It implicitly contrasts with the narrower sibling readers like wem_get_parameters and wem_read_parameters, but never names them, so the differentiation is inferred rather than stated.
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?
"Useful for getting a full picture of the heating system state" implies when to reach for it, but no explicit when-not condition or named alternative is given. An agent must guess whether to call this instead of wem_get_devices + wem_get_parameters or wem_get_device_status.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.