mcp-server-zwave-js-ui

Overview Schema Source Related Servers Discussions Admin

zwave_reinterview_node

Re-run a Z-Wave node's interview to refresh its capabilities and values. Useful when a device's reported information is outdated or incomplete, helping restore accurate communication.

Instructions

Re-run a node's interview to refresh its capabilities and values.

Fire-and-forget: returns once the interview is requested; the interview itself runs in the background and can take a while for battery devices. Raises ValueError for an unknown node id.

Args: node_id: The Z-Wave node id, e.g. 5

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": {
      "node_id": "<node_id>"
    },
    "name": "zwave_reinterview_node"
  }
}

Input Schema

Name	Required	Description	Default
`node_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0Jul 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, but the description discloses async nature, potential delays, and error behavior. It does not explicitly state if the operation is destructive or read-only, but the context suggests it modifies state; overall transparency is good.

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 two short paragraphs: first line states purpose, second adds behavioral details. Every sentence is informative, no fluff.

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?

While the description explains the process and errors, it does not mention the return value (likely nothing or a confirmation). Since there is no output schema, this omission reduces completeness for a fire-and-forget tool.

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?

The description adds meaning to the sole parameter node_id by providing an example ('e.g. 5') and clarifying it's a Z-Wave node id. This adds value beyond the input schema, which has 0% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool re-runs a node's interview to refresh capabilities and values, using a specific verb and resource that distinguishes it from siblings like zwave_node_info or zwave_rebuild_node_routes.

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?

Describes fire-and-forget behavior, background execution, delay for battery devices, and ValueError for unknown nodes. While it doesn't explicitly contrast with siblings, the guidance is clear and practical.

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