No user-submitted related servers found.
Scored across 17 tools
Most tools target clearly distinct operations: app lifecycle (install/launch/terminate/list), UI interaction (tap/swipe/type), and accessibility inspection (describe_all/describe_point/find_element) are all well-separated. The main ambiguity is ui_view vs screenshot, which both return an image of the simulator screen, plus ui_describe_point vs ui_find_element which are similar but distinguishable by input (coordinates vs criteria).
Nearly all names are snake_case verb_noun and readable, with an apparent two-namespace convention (ui_ prefix for interaction, plain verbs for simctl/app management). The main deviation is 'screenshot', a bare noun that also lacks the ui_ prefix used by its near-twin 'ui_view', creating a minor pattern break.
17 tools sits at the upper end but each maps to a concrete, non-redundant capability (screen capture, recording, accessibility, input, app management). The surface is broad but reasonably justified for a full simulator-control server, though the ui_view/screenshot pair could be consolidated to trim one.
Coverage is strong: state detection, app install/launch/terminate/list, URL/deep-link handling, screenshots, video recording, UI input, and accessibility inspection are all present. Gaps remain around simulator lifecycle (no explicit boot/shutdown of a specific device, only get_booted_sim_id/open_simulator) and app management (no uninstall_app), but these are minor and workable.