Skip to main content
Glama
chanyou0311

aiseg2-mcp

by chanyou0311

get_history

Read-onlyIdempotent

Retrieve long-term energy data from a Panasonic AiSEG2 home energy controller, with selectable time resolution and filters for metrics and circuits, supporting pagination.

Instructions

Read-only. Query the AiSEG2's long-term energy history from its SD-card export (values in Wh).

Requires an SD card inserted in the AiSEG2. The export is downloaded once and cached, so the
first call is slow and later calls are fast. Returns long-form points ({timestamp, metric,
value}); use limit/offset to page (limit caps the number of returned points).

Args:
    granularity: Time resolution. "30min"/"hour"/"day" take start/end as YYYY-MM-DD; "month"
        takes YYYY-MM; "year" takes YYYY.
    start: Range start (inclusive), formatted per the granularity.
    end: Range end (inclusive), formatted per the granularity.
    metrics: Optional filter by standard series keys (e.g. "generation_pv1", "grid_buy",
        "grid_sell", "battery_charge", "battery_discharge", "ev_charge") or their Japanese
        header names. Omit for all series.
    circuits: Optional filter by circuit name (see list_circuits). Omit for all circuits.
    limit: Maximum number of series points to return (default 200).
    offset: Number of points to skip (for pagination).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYes
limitNo
startYes
offsetNo
metricsNo
circuitsNo
granularityYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitYes
seriesYes
has_moreYes
total_rowsYes
granularityYes
next_offsetNo
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint), the description discloses valuable behavioral details: the SD-card requirement, caching behavior with first call latency, return format as long-form points, and limit/offset pagination semantics. This significantly informs the agent.

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 well-structured with a summary sentence, requirements, behavior notes, and an Args list. Every sentence provides useful information without repetition or fluff, making it efficient despite its length.

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?

The description covers all aspects needed to use the tool: purpose, prerequisites, caching behavior, return format, and full parameter semantics. Given the output schema exists, return values need no further explanation, making the description complete.

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

Parameters5/5

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

With 0% schema description coverage, the description entirely compensates by explaining every parameter in detail: granularity-specific date formats, standard metric keys, circuit filtering, and limit/offset defaults. This adds meaning far beyond the bare schema types.

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 description clearly states the tool queries the AiSEG2's long-term energy history from its SD-card export, with a specific verb and resource. It does not explicitly differentiate from sibling tools like get_daily_totals or get_cost_history, so it misses the top score.

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 provides clear context for when to use the tool: it requires an SD card, notes the first call is slow due to caching, and explains pagination. However, it does not mention alternatives or when not to use it, so it lacks explicit exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/chanyou0311/aiseg2-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server