VoltWise MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VOLTWISE_MODE | No | Runtime mode (SIMULATION or PRODUCTION). | SIMULATION |
| VOLTWISE_DB_PATH | No | Path to the SQLite event and trace database. | data/voltwise.db |
| VOLTWISE_MCP_URL | No | URL used by the REST gateway to reach MCP. | http://127.0.0.1:8001/mcp |
| VOLTWISE_MCP_HOST | No | Bind address for the MCP Streamable HTTP server. | 127.0.0.1 |
| VOLTWISE_MCP_PORT | No | Port for the standalone MCP HTTP server. | 8001 |
| VOLTWISE_PUBLIC_DEMO | No | Enables HTTP Basic challenge and bearer tokens for public demo staging. | false |
| VOLTWISE_CORS_ORIGINS | No | Permitted browser origins. | http://localhost:5173,http://127.0.0.1:5173 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| power_control_deviceC | Control a simulated household device (light, fan, TV, AC, dishwasher). |
| power_turn_on_and_verifyC | Turn on a simulated device and verify its direct electrical response. |
| power_run_diagnosticB | Verify, diagnose, safely retry when permitted, and re-verify a device. |
| power_compare_periodsB | Compare current-cycle energy with the equivalent previous-cycle period. |
| power_explain_usage_changeC | Rank observed contributors and preserve unattributed household usage. |
| power_get_tariff_statusB | Return current and projected position under the illustrative demo tariff. |
| power_forecast_billB | Estimate current and projected energy charges, not a complete utility bill. |
| power_estimate_load_impactC | Estimate a configured appliance operation's energy and incremental charge. |
| power_suggest_actionsC | Return evidence-based actions and optional target-consumption guidance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools target distinct analytical tasks, but three tools cluster around device control/verification: power_control_device, power_turn_on_and_verify, and power_run_diagnostic all involve turning on and validating a device, with the latter two appearing as narrower subsets of the first. An agent may struggle to pick between them, though the tariff/forecast/explain tools are clearly separated.
Every tool uses the same power_ prefix followed by a snake_case verb_noun phrase (power_control_device, power_compare_periods, power_forecast_bill), giving a highly predictable, uniform pattern.
Nine tools is well within the ideal range and each maps to a distinct energy-management capability (control, diagnostics, comparison, explanation, tariff, forecast, load impact, suggestions). The set is scoped tightly with no filler.
The surface covers the full monitoring-to-action lifecycle including control, diagnostics, analysis, billing projection, and recommendations. Minor gaps exist, such as no explicit device discovery/listing or standalone scheduling tool, but core workflows are reachable.