Growatt MCP Server

get_devices

Read-onlyIdempotent

Retrieve all devices for a specific plant or your entire account, with device types like min, sph, or max, to identify which device other tools should target.

Instructions

List devices with their type ("min", "sph", "max", ...), which the other tools need.

With a plant_id, returns every device of that plant (page is ignored). Without it, returns all devices on the account, paginated.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number, starting at 1.
`plant_id`	No	Plant ID, as returned by get_plants. Empty means all plants.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 21, 2026

TDQS

A4.4/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark the call read-only, idempotent, and non-destructive. The text adds concrete behavior: device type values, plant scoping, pagination only when no plant_id is provided, and the fact that page is ignored in the plant-scoped branch.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying information: what is returned, the plant-scoped behavior, and the unscoped paginated behavior. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two optional parameters, strong annotations, and an output schema, no critical invocation details are missing. The description covers scope, pagination, and type output, which is sufficient for correct use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents both parameters at 100% coverage, so the baseline is 3. The description adds the non-obvious relationship that page is ignored when plant_id is supplied and defines the scope of the unfiltered call, which meaningfully improves invocation correctness.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource ('List devices') and states that the output includes the device type needed by other tools. This makes the tool's role clear, though it does not explicitly contrast it with siblings like get_device_info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit conditional guidance: with plant_id all devices for that plant are returned and page is ignored; without it the call is paginated over the account. This tells the agent how to vary arguments, though it does not name alternatives such as get_device_info for detail lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.