Related Servers

Descriptions are exceptionally detailed with cross-references, but at 286 tools genuine boundary-blurring pairs exist: moldability_screen/moldability_check/optics_moldability_check/dfm_check all screen moldability, measure_distance vs min_clearance overlap, and fillet_edges vs partdesign_fillet require reading deep into descriptions to disambiguate. A capable agent can navigate most pairs, but the sheer surface area makes misselection likely.

The verb_noun pattern is upheld across well-organized prefix families (add_*, make_*, list_*, fem_*, cfd_*, em_*, sheet_*, *_submit, *_check), and the sync/async pairing via submit/job_status/job_result is exemplary. Deviations exist — bare PartDesign feature nouns (hole, pad, pocket) next to verb-prefixed tools, the confusing fit_check vs fit_class pair, and outliers like ping, version, and where_used — but the dominant convention is clear and predictable.

286 tools is an extreme mismatch for an agent-facing MCP surface, far beyond even the 50+ threshold for the lowest score. The server attempts to cover CAD modeling, FEM, CFD, DEM, optics, acoustics, EM, thermal, sheet metal, drawings, PLM, and project management in one namespace, and the resulting context-window and tool-selection burden undermines every other coherence dimension.

Coverage within each family is remarkably complete: CRUD-like lifecycles exist for sketches, bodies, assemblies, drawings, items, recipes, features, and ECOs; every solver family pairs an analytic oracle with a *_submit solve and a gate. Minor gaps include no delete_object/remove_feature tool (only transaction_abort) and no STEP/IGES import to complement export_shape, but these are workable rather than blocking.