No user-submitted related servers found.
Scored across 19 tools
Several tools overlap in purpose: element_action (by ref) vs element_action_at (by skyshot index) perform virtually the same UI Automation action through different handles, and click_at, type_text, and element_action(set_value) can all deliver input to a control. The very detailed descriptions do help tell them apart (ref vs index, soft vs physical input), so an agent can navigate it, but the boundaries are not clean.
Every name is prefixed with tool_ and uses snake_case, giving a predictable surface. Most follow verb_noun (type_text, capture_window, list_windows), though a cluster of element/clipboard tools is noun-first (element_action, element_at_point, clipboard_read), a minor deviation rather than a real inconsistency.
19 tools is on the heavy side but splits cleanly across a broad domain (windows, elements, input, displays, clipboard, app launch, coexistence). Each entry maps to a distinct capability, so the count is justified despite being near the upper comfortable range.
Coverage of the desktop-automation lifecycle is strong: window/element discovery, tree-based and coordinate-based acting, keyboard, text typing, screenshots, clipboard, displays, and app launching are all present. Gaps are minor (no drag-and-drop, explicit scroll-wheel, or window move/resize/close), which agents can largely work around.