Retrieve real-time operational data for a MAX-series inverter by providing its serial number, enabling immediate monitoring of solar performance and system status.
Get the latest data for one MAX-series inverter.
| Name | Required | Description | Default |
|---|---|---|---|
| device_sn | Yes | MAX inverter serial number. |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorld). The description adds the temporal scope ('latest') and cardinality ('one'), which is useful context, but it does not disclose operational behavior such as missing-device handling or data freshness guarantees.
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 one short, front-loaded sentence with no filler. Every word contributes meaning, and key scope information ('latest', 'one', 'MAX-series') is included efficiently.
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 a tool with one required parameter, a rich annotation set, and an output schema, the description is nearly sufficient. It could clarify what 'latest data' includes, but the output schema likely covers return structure, so this is a minor gap.
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%, with device_sn already described as 'MAX inverter serial number.' The description reinforces this by referring to a single MAX-series inverter but adds no new parameter-level meaning beyond the schema.
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 clear verb ('Get') with a specific resource ('latest data for one MAX-series inverter') and cardinality ('one'). It is unambiguous enough to be useful, though it does not explicitly distinguish itself from siblings like get_max_batch_data or get_device_last_data.
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 wording suggests this tool is for a single MAX inverter's latest data snapshot, which gives clear context. However, it does not explicitly state when not to use it or name alternatives such as get_max_batch_data for multiple devices.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.