No user-submitted related servers found.
Scored across 26 tools
Most tools are cleanly separated by gesture or resource (tap vs long_press vs double_tap vs drag vs swipe), and the observe/find/wait trio has clear boundaries (read tree, locate selector, block for condition). The fuzziest pairs are aua_swipe vs aua_scroll_until (both motion-based, though one targets a selector) and aua_screen/aua_screen_frame/aua_screen_action, which require reading descriptions carefully. aua_execute_goal vs aua_goal_decide is well explained as an auto/host decider pair.
All 26 tools share the aua_ snake_case prefix with mostly verb-based names (aua_tap, aua_launch_app, aua_read_fields, aua_execute_goal). A few outliers are nouns/adjectives rather than verbs (aua_screen, aua_apps, aua_doctor, aua_ready), a minor deviation. The convention remains predictable despite the large set.
26 tools is at the heavy end — the rubric's 'borderline/heavy' band. Android UI automation is genuinely broad (gestures, observation, vision, goal-driving, setup, diagnostics), so most tools map to real capabilities, but a few niche ones (aua_screen_frame, aua_screen_action, aua_pause/aua_resume) inflate the surface and add selection cost.
Coverage is strong for device automation: gesture input, observation, find/wait, app launching, batching, setup/diagnostics, and a goal-driven loop. Gaps are smaller: no app install/uninstall or force-stop, no file/ADB shell passthrough, and key input limited to home/back/recent/enter/volume. These are workable around but leave a few dead ends.