No user-submitted related servers found.
Scored across 10 tools
Tools are cleanly partitioned by UI object type (session, app, window, field, form, table, doc, calendar, find, scenario), and descriptions explicitly cross-reference where sibling actions live, e.g. 'tc_field(action="is_visible")' from tc_app. A few boundaries still blur — tc_app vs tc_window for window/app state, tc_app.get_child_objects vs tc_find, and tc_field vs tc_form for focus/activation — but the disambiguation notes on each tool substantially mitigate these.
Every top-level tool follows the same tc_<noun> pattern (tc_session, tc_app, tc_window, tc_field, tc_form, tc_scenario, tc_find, tc_doc, tc_table, tc_calendar). Actions within each group are uniformly snake_case verb_noun (get_active_window, set_cell_text, goto_next_row), so the whole surface is predictable.
Ten top-level tools is well-scoped for a UI-test-automation server; each namespace maps to a coherent domain (session lifecycle, app state, window, element kinds, discovery, recording) rather than duplicating a peer. The heavy per-group action lists are a deliberate dispatch pattern, not tool sprawl.
Coverage spans the full lifecycle: connect/launch/stop clients, inspect app and window state, read and edit every element kind (field, table, document, calendar), search the UI tree, and record/replay scenarios. Deprecated aliases are retained (get_area_text vs get_current_area_text), and no obvious end-to-end workflow dead-ends.