No user-submitted related servers found.
Scored across 63 tools
Most tools are individually well-scoped, but several near-overlap pairs exist: get_dtm_dataset vs get_master_dtm_dataset, set_dtm_dataset vs set_master_dtm_dataset, and place_fb_in_ladder vs use_fb_in_ladder. With 63 tools, an agent must parse long descriptions to avoid misselecting, especially among DTM/ladder helper variants.
The surface is consistently snake_case, but verb prefixes are mixed: new_project vs create_*, change_cpu vs replace_*, get_project_setting singular vs set_project_settings plural, and place_fb_in_ladder vs use_fb_in_ladder. The pattern is readable but not predictable enough to infer tool relationships.
63 tools is far above the 3-15 well-scoped range and even the 16-25 heavy range; many narrow helpers could be consolidated (two ladder FB placers, four DTM dataset variants). The breadth may match Control Expert's complexity, but as an MCP surface it imposes a heavy selection burden.
Core project, variable, section, hardware, DTM, and simulator operations are present, but the documented workflow references plc_connect, plc_transfer, and plc_command tools that do not exist, leaving online transfer/control incomplete. Other gaps include no delete_task, no data-type creation, and no RemoteConnect import step despite the bulk-edit workflow.