No user-submitted related servers found.
Scored across 129 tools
Many tools have overlapping purposes: field_dropdown_close vs field_dropdown_state vs field_dropdown_items, table_* tools are numerous and similar, and ui_tree_resource_* tools plus ui_tree itself create ambiguity. The descriptions help somewhat, but an agent could easily pick the wrong tool among the many table, field, and dynamic_list variants.
Most tools follow a verb_noun pattern (e.g., save_form, close_form, table_add_row, dynamic_list_find), but there are inconsistencies: some use noun_verb (rag_source_add, field_dropdown_close), some are vague (process, run, execute, do_thing), and one tool has a leading underscore (_metadata_objects_from_catalog_impl). The mixed conventions reduce predictability.
129 tools is far beyond the typical well-scoped MCP server. Even for a complex 1C testing platform, this is an extreme number that will overwhelm agents and make selection difficult. The count alone indicates poor coherence.
The tool surface is extremely comprehensive for the 1C testing domain: it covers session management, RAG indexing, UI navigation, form/table operations, dynamic lists, tabular documents, credentials, recording, and diagnostics. There are minor gaps (e.g., no explicit tool for editing tabular document cells, no direct report export beyond tabular_document_save), but the domain is thoroughly covered.