No user-submitted related servers found.
Scored across 28 tools
Most tools map to a distinct action+target (install_app vs launch_app vs terminate_app, list_apps vs list_app_files, tap vs tap_element vs double_tap vs long_press). Minor overlap remains: scroll is essentially a directional convenience over swipe, and tap_element implicitly waits for an element like wait_for_element, but the descriptions make the intended split clear enough that misselection is unlikely.
The set is overwhelmingly verb_noun snake_case (open_url, install_app, launch_app, get_app_logs, set_orientation, pull_file). Deviations are bare verbs/nouns for gestures and capture (tap, swipe, scroll, long_press, screenshot, describe_ui), which are conventional and still readable, but slightly break the pattern.
28 tools is on the heavy side, but the domain genuinely spans device selection, app build/install lifecycle, UI automation, input, media, and file extraction, and nearly every tool earns its place. The count is defensible rather than padded, though the driver start/stop pair could be folded into automatic management.
Coverage is broad and closed-loop: build → install → launch → interact → inspect → pull logs/files → terminate/uninstall, plus orientation, volume, audio, and screenshots. The main gap is one-directional file access—pull_file exists but there is no push_file/upload into an app container—plus no video capture, both of which agents can work around or that fall outside the core purpose.