Philips Hue MCP server + Claude Code hooks — ambient light as a visual state indicator
Airglow demonstrates solid naming conventions (verb_noun pattern: setup, discover_bridge, create_user, get_lights, set_light, set_group, set_status, activate_scene) and comprehensive parameter schemas with type definitions and descriptions. Tool descriptions are present and contextual (avg ~120 chars), explaining WHAT each tool does and WHEN to use it. However, several critical gaps reduce the score: (1) Output schemas are not documented, callers cannot predict response structure; (2) Error handling lacks recovery guidance, no indication of retryability or next steps; (3) Parameter descriptions omit constraints (e.g., brightness 0 - 100 lacks min/max validation guidance); (4) No pagination support despite tools returning lists (get_lights, get_groups, get_scenes); (5) Missing idempotency hints on write operations. The setup() tool is well-designed for discovery, but set_light/set_group lack confirmation patterns for destructive state changes.
Activate a saved scene on a group or room.
Register a new user on the Hue bridge. Press the physical link button first, then call this within 30 seconds.
Discover Philips Hue bridges on the local network via N-UPnP.
List all groups and rooms on the bridge.
List lights on the bridge with their current state. Filterable by room, on/off state, or color capability.
List all saved scenes on the bridge.
Output schemas not documented. Callers cannot predict response structure (e.g., what fields does get_lights() return? Is it {lights: [...]} or {data: [...]}?). LLMs cannot plan downstream tool calls without knowing available fields.
Error handling lacks recovery guidance. No indication whether errors are retryable, user-fixable, or fatal. E.g., 'Bridge not configured' should suggest 'Call setup() to get started', currently just rejects with generic message.
No pagination support for list tools (get_lights, get_groups, get_scenes). If a user has 100+ lights, response will be massive and blow context window. Should accept limit/offset and return total_count.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Control all lights in a group or room — on/off, brightness, color, scene, transition time.
Control an individual light — on/off, brightness (0–100%), color temp, RGB, HSL, flash alert, transition time.
Set the status color of the default group or hook light. Predefined states: idle, thinking, working, building, waiting, success, deployed, error, alert, pulse_once, off.
Smart onboarding tool. Checks configuration state, auto-discovers the bridge if needed, lists lights and zones for selection, and returns the exact next step required. Always call this first if you are unsure whether the bridge is configured.
Write operations (set_light, set_group, set_status, activate_scene) lack confirmation/dry-run pattern. Agents can accidentally turn off all lights or activate wrong scene without safeguard. Should support a 'dry_run' parameter or require explicit confirmation.
Parameter descriptions lack explicit constraints. E.g., brightness '0 - 100 percent' is stated but no min/max validation guidance. Color temp '153 (cool) to 500 (warm)' lacks clarity on whether values outside this range are clamped or rejected.