No user-submitted related servers found.
Scored across 18 tools
Each tool has a stated boundary, and descriptions actively fence off overlaps (e.g. aua_screen_frame 'does not query UI trees or capture screenshots', aua_ready 'does not start/restart services'). However, the clusters aua_observe/aua_ready/aua_find and aua_screen/aua_screen_frame/aua_screen_action are close enough that an agent could misselect without careful reading, especially since all three observation tools return tree/screenshot-like data.
All 18 tools share a consistent aua_ snake_case prefix with lowercase, readable names. The only deviation is verb-based names (aua_tap, aua_swipe, aua_launch_app) mixed with noun/adjective names (aua_screen, aua_ready, aua_apps, aua_doctor), though the prefix makes the set predictable.
18 tools is on the heavier side of the suggested range, but each covers a distinct capability: core input primitives (tap/type/swipe/press), observation (observe/find/wait), batching, app management, and session/streaming infrastructure. The seven session/diagnostic tools (setup, ready, doctor, pause, resume, screen, screen_frame) inflate the count slightly but are defensible for a device-automation server.
The surface covers the core automation lifecycle: launch, inspect, find, tap, type, swipe, hardware buttons, wait, and batch execution, plus app listing and live screen streaming. Minor gaps exist — no force-stop/app data reset (explicitly excluded from launch), no long-press, pinch/multi-touch, or install/uninstall — but agents can mostly work around these via swipes and external ADB.