Skip to main content
Glama
cacack

mcp-server-zwave-js-ui

by cacack

zwave_node_info

Retrieve complete details for a single Z-Wave node, including device class, command classes, endpoint count, security class, protocol version, last-seen time, and signal statistics.

Instructions

Get full detail for a single Z-Wave node.

Includes device class, supported command classes, endpoint count, security class, protocol version, last-seen time, and signal statistics, on top of the summary fields. protocol_version is a {"value": int, "label": str} object (label is null for an unmapped code). Raises ValueError if the node id is unknown.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idYes
Behavior4/5

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

With no annotations, description carries full burden. Discloses error handling (ValueError) and the special structure of protocol_version. Could mention more about return format but sufficient.

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?

Front-loaded with purpose, includes docstring. Slightly verbose with protocol_version detail but not excessive. Well-structured.

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?

No output schema, but description enumerates returned fields (device class, command classes, etc.) and highlights protocol_version shape. Covers key aspects for a single-node detail tool.

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?

Schema coverage is 0%, but description adds parameter name, type, and example (node_id: integer, e.g., 5). Adds meaning beyond bare schema.

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?

Clearly states 'Get full detail for a single Z-Wave node,' specifying verb and resource. Distinguishes from sibling tools like zwave_list_nodes (list) and zwave_node_config (config).

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

Usage Guidelines3/5

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

No explicit guidance on when to use vs alternatives, though the purpose implies single-node detail. Mentions ValueError for unknown node_id, which is helpful but not a usage guideline.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cacack/mcp-server-zwave-js-ui'

If you have feedback or need assistance with the MCP directory API, please join our Discord server