VoltWise MCP Server

Overview Schema Source Related Servers Discussions Admin

power_turn_on_and_verify

Turn on a simulated device and check its direct electrical response to verify smart-home commands produce expected results.

Instructions

Turn on a simulated device and verify its direct electrical response.

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_turn_on_and_verify"
  }
}

Input Schema

Name	Required	Description	Default
`device`	Yes

Output Schema

Name	Required	Description	Default
`device`	Yes
`reason`	Yes
`command`	Yes
`confidence`	Yes
`verification`	Yes
`reported_state`	Yes
`evidence_source`	Yes
`confidence_level`	Yes
`speakable_summary`	Yes
`telemetry_available`	Yes
`expected_power_watts`	Yes
`observed_power_watts`	Yes
`diagnostic_classification`	Yes
`observed_power_delta_watts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It implies a mutation (turning a device on) plus a verification step, but never says what happens on failure, whether the operation is idempotent or reversible, what permissions are needed, or what the verification result contains.

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 wasted words. It is appropriately sized for the payload, though the terseness is part of why other dimensions are thin.

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

Completeness2/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 for a mutation tool with zero annotations and an undocumented parameter the description is too thin. It omits side effects, failure behavior, and the device identifier format an agent needs to call it correctly.

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?

Schema description coverage is 0% for the single required 'device' parameter, so the description must compensate and does not. It never indicates whether 'device' expects an ID, a name, or a constrained set of values.

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 states a specific compound verb+resource: turn on a simulated device and verify its direct electrical response. It is clear what the tool does, but it does not distinguish itself from the sibling power_control_device, which plausibly also switches devices on, leaving the agent to guess which one to pick.

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 mention of prerequisites, and no reference to any alternative such as power_control_device. The only contextual hint is the word 'simulated', which does not route the agent between siblings.

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

Deploy Server