No user-submitted related servers found.
Scored across 17 tools
The three code-execution tools (execute_code, execute_code_async, execute_code_headless) share a purpose, but their descriptions draw very explicit boundaries: GUI thread vs. background thread with commit(), vs. separate headless freecadcmd process. Similarly, create_object vs. edit_object is clarified by edit_object's note that it is the fallback when create_object cannot handle the type. Some cognitive load remains in choosing among the execution variants, but the guidance resolves it in practice.
Nearly all tools follow a verb_noun convention (create_document, list_documents, create_object, edit_object, delete_object, get_object, get_objects, get_view, reload_document, run_fem_analysis), with a coherent shared prefix for the execute_code family. Minor deviations exist: get_parts_list reverses the noun/verb order compared to list_documents, and status getters use get_*_status. Still highly readable and predictable overall.
17 tools is at the upper end but each maps to a real capability (document lifecycle, object CRUD, inspection/screenshots, three execution modes, parts library, FEM solving, diagnostics). Nothing looks like padding, and the split of execution modes is justified by real threading hazards in FreeCAD. A slightly lighter surface might merge get_object/get_objects or get_parts_list/insert_part_from_library, but the count is reasonable for the scope.
Object-level CRUD is fully covered (create/get/list/edit/delete), documents can be created, listed, and reloaded, and there is rendering, scripting, a parts library, diagnostics, and an FEM solve path. Gaps exist around document lifecycle and I/O: there is no explicit close_document, save_document, or STEP/STL import/export tool, though these are reachable via execute_object/create_object properties and the execute_script tools. Agents can work around the gaps, so coverage is strong but not seamless.