Scored across 48 tools
Despite 48 tools, each targets a distinct resource or feature class: session management, geometry analysis, feature recognition, rendering, and export are clearly separated. A few pairs could be confused (measure vs inspect_part, find_bosses vs find_bored_bosses), but descriptions draw clear boundaries, and deprecated tools are explicitly marked as replacements.
Tool names are consistently snake_case with a verb-first pattern for actions (find_*, render_*, save_*, execute, compare, validate). Minor deviations exist where nouns are used as commands (session_state, version, health_check), and one spelling inconsistency ('recognise' vs 'analyze'), but there is no mixing of naming conventions.
48 tools is well beyond the comfortable range, and six of them (lint_drawing, suggest_view_layout, inspect_drawing, render_drawing, save_drawing_annotations, view_axes) are deprecated placeholders that only explain their replacement. While the server's scope is broad (CAD modeling, analysis, feature recognition, drawing, import/export, repair), the sheer number makes the surface heavier than typical MCP servers.
The tool surface covers the full modeling/analysis lifecycle: code execution, geometry measurement, feature recognition, edit transactions, validation, repair guidance, snapshots, import/export, and session management. Minor gaps exist (e.g., no direct parameter-edit tool beyond design_audit, drawing creation moved out), but agents can work around them via execute().