No user-submitted related servers found.
Scored across 20 tools
Each tool has a clearly distinct purpose and resource/action, with overlapping pairs (e.g., check_process vs. list_processes, list_windows vs. get_taskbar) explicitly disambiguated in their descriptions. The ui_* tools are further segmented by operation (find, read, invoke, set_value), leaving no ambiguity.
Tool names predominantly follow a verb_noun snake_case pattern (get_, list_, check_, report_), but a few deviations like 'health_check' and 'wait_for' break consistency. The ui_* prefix creates a coherent subgroup, though it mixes verb positions (ui_find vs. ui_set_value).
At 20 tools, the server is on the heavy side but each tool earns its place given the combined scope of process monitoring, UI automation, and telemetry. The count slightly exceeds the comfortable 3-15 range but is not bloated.
The tool set covers core workflows: observing processes/windows, reading and interacting with UI, waiting for conditions, and reporting outcomes. Notable gaps include lack of direct process start/termination and no file management beyond single-file checks, which agents may need to work around.