VoltWise MCP Server

Overview Schema Source Related Servers Discussions Admin

power_get_tariff_status

Retrieve current and projected charges under an illustrative demo tariff to track your energy position and forecast costs.

Instructions

Return current and projected position under the illustrative demo tariff.

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": "power_get_tariff_status"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`source`	Yes
`is_demo`	Yes
`currency`	Yes
`tariff_id`	Yes
`tariff_name`	Yes
`tariff_type`	Yes
`current_slab`	Yes
`projected_slab`	Yes
`current_usage_kwh`	Yes
`speakable_summary`	Yes
`threshold_warning`	Yes
`next_marginal_rate`	Yes
`next_threshold_kwh`	Yes
`current_marginal_rate`	Yes
`projected_month_end_kwh`	Yes
`units_until_next_threshold`	Yes
`expected_threshold_crossings`	Yes
`current_estimated_energy_charge`	Yes
`projected_estimated_energy_charge`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It adds the useful context that the tariff is an 'illustrative demo' rather than real billing data, and 'Return' implies a non-mutating read, but it says nothing about permissions, data freshness, or scope limits. Adequate for a zero-parameter read, but not rich.

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?

A single front-loaded sentence with no filler, correctly leading with the action and resource. It is tight, though the term 'position' is left unqualified and does no extra work.

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 the description need not enumerate return values, and with zero parameters the surface is small. It is complete enough to invoke, though the ambiguous word 'position' (tier? rate? standing?) means the description relies entirely on the output schema to explain what is actually returned.

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 takes no parameters, so there is nothing for the description to disambiguate and the baseline is 4. No syntax or format detail is needed.

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 (return) and resource (tariff status / current and projected position), so the agent knows this is a read of tariff standing rather than a device or billing action. It does not explicitly contrast itself with siblings like power_forecast_bill or power_compare_periods, which could plausibly overlap in the tariff/billing space, 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 statement of when to reach for this tool versus power_forecast_bill or power_compare_periods, and no prerequisites or exclusions. The agent is left to infer the use case purely from the tool name.

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

Deploy Server