No user-submitted related servers found.
Scored across 28 tools
Tools are cleanly organized by resource type (devices, system variables, programs, rooms, CCU targets), so most purposes are unmistakable. Mild ambiguity exists between get_value/get_values, set_value/put_paramset, and execute_program/run_script, though the descriptions do draw clear lines between them.
Every tool follows a consistent verb_noun snake_case convention, with tidy prefixes: list_* for enumeration, get_* for reads, set_/put_/create_/delete_ for writes, and precise action verbs (assign, execute, acknowledge, use). Even put_paramset vs set_value maps to a meaningful full-resource vs single-datapoint distinction.
28 tools is above the typical ideal range, but the server covers an unusually broad domain: device I/O, paramsets, system variables, programs, rooms/functions, links, service messages, RSSI diagnostics, and multi-CCU target management. There is little redundancy — apparent duplicates like get_value/get_values and get_connection_info/list_ccu_targets are justified single-vs-batch or detail-vs-list splits.
Core lifecycles are covered well: system variables have full list/set/create/delete, channels have single and bulk read/write, rooms and functions have assign/unassign, and service messages have get/acknowledge. Notable gaps are program creation/editing and link creation/deletion (list_links is explicitly read-only), but run_script provides a documented universal escape hatch that mitigates most dead ends.