MCP server for Solar Manager (https://www.solar-manager.ch). Covers both APIs: the Cloud API at cloud.solar-manager.ch — history, forecast, tariffs, device control; and the local API on the gateway itself — live values, no internet needed.
Solar Manager MCP has clear, well-structured tool definitions with good naming conventions (verb_noun pattern: list_, describe_, request, local_live). All four tools have descriptions and input schemas. However, parameter descriptions are minimal or missing context about constraints, formats, and dependencies. The `request` tool lacks output schema documentation. Error handling is present but not recovery-focused. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles. Descriptions are adequate (100-200 chars) but could better explain WHEN to use each tool and dependencies between them.
Show parameters and response schema of one endpoint, e.g. path="/v3/users/{smId}/data/range", method="get".
List Solar Manager API endpoints, optionally filtered by a substring (matched against path, summary and tag, e.g. "battery", "forecast", "v3").
Live values straight from the Solar Manager gateway on the local network (no cloud, no internet): production, consumption, battery, and per-device power with device names resolved. Needs SOLAR_MANAGER_LOCAL_URL + SOLAR_MANAGER_LOCAL_API_KEY.
Call a Solar Manager endpoint. `path` must have placeholders already filled in, e.g. "/v3/users/abc123/data/range" with query {"from": "...", "to": "...", "interval": 3600}. PUT endpoints physically control hardware (battery, chargers, heat pumps) and are blocked unless SOLAR_MANAGER_ALLOW_CONTROL=1 is set.
Output schemas not documented. Tools return JSON strings but LLMs cannot infer field structure. `request` and `local_live` return truncated JSON (MAX_CHARS=40000) with no schema guidance for downstream tool chaining.
Parameter descriptions lack format/constraint details. `path` parameter in `describe_endpoint` and `request` should specify format (e.g., 'must start with /', placeholders like {smId}). `method` should be an enum (GET, POST, PUT, DELETE) not a free string.
No tool annotations despite clear risk profiles. `request` tool with PUT/DELETE methods is destructive and requires SOLAR_MANAGER_ALLOW_CONTROL=1 guard, but lacks destructiveHint annotation. `list_endpoints` and `describe_endpoint` are read-only but lack readOnlyHint.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Error messages are informative but not recovery-guided. When `request` is blocked (SOLAR_MANAGER_ALLOW_CONTROL not set), it returns a message but does not suggest next steps. When `local_live` fails due to missing env vars, it tells user to set them but does not offer fallback (cloud API).
Discovery tools (`list_endpoints`, `describe_endpoint`) lack guidance on when to call them. Descriptions do not explain that `list_endpoints` should be called first to explore API, or that `describe_endpoint` is needed before `request` to understand parameters.