aiseg2-mcp

get_power_flow

Read-onlyIdempotent

Retrieve live whole-home power flow from AiSEG2: current generation, consumption, grid buy/sell status, battery status, generation sources, and top consuming circuits.

Instructions

Read-only. Get the AiSEG2's instantaneous whole-home power flow right now.

Returns current generation and consumption (kW), whether the home is buying or selling grid power, storage-battery status if a battery is connected, the per-source generation breakdown, and the top consuming circuits at this moment.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_power_flow"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`battery`	No
`buy_sell`	Yes
`generation_kw`	Yes
`top_consumers`	No
`consumption_kw`	Yes
`generation_detail`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior, so the description adds value by detailing what data is returned and under what conditions (e.g., 'if a battery is connected'). It goes beyond the annotations by specifying the return contents, although it does not discuss error cases or access requirements.

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?

The description is two sentences long, front-loads the read-only and time-sensitive nature, and packs useful detail into a compact list of return categories. Every sentence earns its place, with no redundancy or filler.

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?

Given the tool's moderate complexity, zero parameters, and existing output schema, the description fully covers what an agent needs: it states the resource, the temporal scope, the return categories, and conditional elements. No critical invocation details are missing.

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 tool has zero parameters and the schema coverage is 100% (empty properties), so there is no parameter meaning to clarify. The baseline for 0-parameter tools is 4, and the description appropriately focuses on output rather than input semantics.

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

Purpose5/5

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

The description uses a specific verb ('Get'), identifies the exact resource ('AiSEG2's instantaneous whole-home power flow'), and clearly scopes it to 'right now.' It enumerates distinct return values (generation/consumption, buy/sell status, battery, per-source breakdown, top circuits) that distinguish it from the historical/circuit-focused sibling tools.

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 clearly conveys real-time, current-state usage through words like 'instantaneous' and 'right now,' which implies use for immediate monitoring rather than historical analysis. It does not explicitly name alternatives like get_history or get_circuit_breakdown, but the context is clear enough for an agent to select this tool for a live snapshot.

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

Deploy Server