VoltWise MCP Server

Overview Schema Source Related Servers Discussions Admin

power_estimate_load_impact

Estimate energy use and incremental electricity charge for a configured appliance operation to assess cost and load before use.

Instructions

Estimate a configured appliance operation's energy and incremental charge.

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": {
      "device": "<device>"
    },
    "name": "power_estimate_load_impact"
  }
}

Input Schema

Name	Required	Description	Default
`device`	Yes

Output Schema

Name	Required	Description	Default
`device`	Yes
`device_id`	Yes
`after_slab`	Yes
`before_slab`	Yes
`after_usage_kwh`	Yes
`before_usage_kwh`	Yes
`informative_only`	Yes
`speakable_summary`	Yes
`threshold_crossed`	Yes
`energy_impact_type`	Yes
`after_energy_charge`	Yes
`before_energy_charge`	Yes
`crossed_thresholds_kwh`	Yes
`estimated_operation_kwh`	Yes
`estimated_incremental_energy_charge`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries the full burden, and it does not say whether this is a pure calculation with no side effects, what permissions it needs, or what 'incremental charge' is relative to. Only the estimate framing implies a read-only simulation, which is inference rather than disclosure.

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?

One tight sentence with the verb and outcome front-loaded and no filler. It is efficient, though its brevity is also the source of the missing context noted elsewhere.

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

Completeness3/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 values need not be explained, but the description still leaves the sole required parameter's meaning and the tool's side-effect profile unspecified. For a one-parameter tool this is minimally adequate but has clear gaps.

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

Parameters2/5

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

The single required parameter 'device' has 0% schema coverage and no description text, and the prose says 'configured appliance operation,' creating ambiguity about whether the argument is a device identifier or an operation reference. The description does not compensate for the coverage gap at all.

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 a specific verb ('Estimate') and resource ('load impact' / energy and incremental charge), which is clearer than the bare name. It does not explicitly differentiate itself from siblings like power_forecast_bill or power_compare_periods, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative. The phrase 'configured appliance operation' hints at a precondition but never states it, leaving the agent to infer when this beats power_forecast_bill or power_compare_periods.

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

Deploy Server