aivy-mcp

Official

Overview Schema Source Related Servers Discussions Admin

get_status

Retrieve live solar and battery system status for a site, including state of charge, PV, load, grid, and battery power readings with source freshness.

Instructions

Live reading: SOC (%), pv_w, load_w, grid_w (>0 exporting), battery_w (>0 charging). A null channel is one the vendor does not report, not zero. source is vendor (fresh) or stored (last kept reading). Hosts that support cards render this as a status card.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "get_status"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.0Nov 6, 2026

TDQS

A3.7/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden and does substantial work: it defines sign conventions (grid_w > 0 exporting, battery_w > 0 charging), explains that null means unreported rather than zero, and clarifies the `source` field as vendor-fresh versus stale-stored. It omits auth requirements and error/rate-limit behavior.

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

Conciseness4/5

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

Dense and front-loaded: the channel list and units come first, followed by null-handling and source semantics. The closing sentence about hosts rendering a status card is marginally tangential but short enough not to waste space.

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

Completeness4/5

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

An output schema exists, so return structure need not be documented, and the description correctly spends its words on interpretation rules (units, sign, nulls, freshness) that a schema cannot convey. The missing piece is guidance on when to prefer this over siblings such as get_site or get_operations.

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

Parameters3/5

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

Only one parameter (site_id) with 0% schema description coverage, and the description never mentions it; it is only implicitly understood as the site being read. With a single self-evident identifier parameter this is a minor gap rather than a harmful one.

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?

States the specific operation (a live reading) and enumerates exactly what it returns: SOC, pv_w, load_w, grid_w, battery_w. The verb 'live reading' plus the channel list makes the resource unambiguous, though it does not explicitly contrast with siblings like get_site or get_operations.

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

Usage Guidelines3/5

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

The word 'Live reading' implies real-time use versus historical tools, and the `source` note (live vs cached last-known) implies this is the go-to for current state. However there is no explicit 'use this when / use X instead' statement and no prerequisites named.

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