No user-submitted related servers found.
Scored across 64 tools
Many tools have overlapping purposes, especially the write_form_value variants (write_form_value, write_form_value_xtest, write_form_values, write_form_fields_by_label), the read_list_* family (column/row/grid), and several assert/read tools. The very detailed descriptions help differentiate them, but an agent still faces non-trivial selection risk across 64 tools with similar naming.
The vast majority of tools use consistent snake_case verb_noun naming (run_scenario, read_record, write_form_value, open_list, select_table_row). A few exceptions are noun-only or diagnostic names (advanced_search, com_connector_doctor, infobase_info, qa_mcp_doctor, role_data_matrix, test_client_status), and one has a suffix (get_window_list_testclient), but the overall pattern is predictable.
64 tools is far above a typical well-scoped set and exceeds the 25+ threshold for 'too many'. The domain is broad (1C client lifecycle, UI automation, scenario running, diagnostics), so some count is justified, but many tools are granular variants of the same underlying operations, making the surface heavier than necessary.
Coverage is extensive: client launch/attach/stop, form and list reads, form/table/cell writes, dialogs, menus, choices, checkboxes, pages, reports, scenario execution, and diagnostics. A few boundaries remain (multi-select read across commands, backward year navigation in date cells, spreadsheet cell decode deferred), but these are minor workarounds rather than glaring gaps.