The server defines 6 tools with clear verb-based names and reasonable descriptions. All tools have proper JSON Schema input definitions with typed parameters and constraints. However, there are systematic gaps in parameter descriptions, missing output schemas, and no tool annotations. The server follows good naming conventions (discover_, get_, set_) and includes timeout parameters with sensible defaults. Parameter constraints like min/max for brightness (0-100) and color temperature (2500-9000) are present. The descriptions are adequate (avg ~100 chars) but lack actionable guidance for error recovery or when to use alternatives. No output schemas are documented, LLMs cannot see what fields to expect from responses. Error handling exists but is not visible in definitions.

• Add output schemas to all tool definitions. Document the structure and types of returned device lists, device info objects, and statistics. Example for discover_devices: {type: 'object', properties: {devices: {type: 'array', items: {type: 'object', properties: {deviceId: {type: 'string'}, host: {type: 'string'}, model: {type: 'string'}, alias: {type: 'string'}}}, total: {type: 'number'}}}
• Add toolAnnotations to tool definitions. Mark read-only tools (discover_devices, get_device_info, get_realtime_stats) with readOnlyHint: true. Mark write tools (set_power_state, set_brightness, set_color_temperature) with destructiveHint: true or idempotentHint if applicable.
• Expand parameter descriptions to clarify deviceId vs. host trade-offs. Example: 'deviceId: UUID or system ID from discover_devices. Preferred if available. host: Device IP address (e.g. 192.168.1.100). Use if deviceId is unknown. If both provided, deviceId takes precedence.'
• Add dependency hints in descriptions. Example for set_power_state: 'Call discover_devices() first to get deviceId and host if you don't have them. Alternatively, provide the host directly if you know the device IP.'
• Document error conditions and recovery paths. For set_brightness: 'Returns error if device does not support brightness control (e.g. smart plugs). Check device model via get_device_info first, or catch error and fall back to set_power_state.'
• Define format constraints for deviceId (e.g. 'UUID format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx') and host (e.g. 'IPv4 address or hostname resolvable on the local network') in parameter descriptions.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained