No user-submitted related servers found.
Scored across 27 tools
Most tools target a distinct action on a distinct resource, and descriptions explicitly cross-reference each other (tap → list_elements, tap_element preference over tap). Minor overlap exists between android_tap and android_tap_element, and between android_swipe and android_drag, but the descriptions clarify when to use which. run_sequence nominally overlaps all input tools, though it is clearly framed as a batching orchestrator.
Almost the whole surface follows an android_verb_noun snake_case pattern (android_list_elements, android_launch_app, android_take_screenshot). The only outlier is run_sequence, which drops the android_ prefix and uses a different verb style. That single deviation keeps it from a 5 but the convention is otherwise highly predictable.
27 tools is above the comfortable range, but the domain (device connection, app lifecycle, input, capture, debugging) is genuinely broad and each tool maps to a real capability. Still, some are borderline granular (android_take_screenshot vs android_save_screenshot, android_double_tap/long_press vs coordinate taps) and could be consolidated.
The surface covers device discovery/connection, app install/uninstall/launch/terminate, rich input, screenshots and video recording, notifications, orientation, and logcat — no major dead ends for UI automation workflows. Gaps remain for file push/pull, clipboard access, arbitrary shell commands, and multi-touch gestures like pinch/zoom.