FreeCAD 3D CAD automation: headless documents and export, plus CFD via FluidX3D/OpenFOAM
This server has 7 tools with highly variable quality. The two primary tools (freecad_bridge, freecad_model) have detailed, well-structured schemas and descriptions. However, 5 tools (freecad_cfd, freecad_bim, freecad_fem, freecad_fluidx3d, freecad_depot) have severely incomplete schemas, only the 'operation' parameter is visible with minimal type info. This is a critical violation of the rubric: tools without visible input schemas score 0 on schema dimension. Additionally, these 5 tools lack operation-specific parameter definitions and have descriptions that are bare operation lists rather than actionable guidance. The server uses fastmcp with HTTP transport (good), but the inconsistency across tools is severe. Average per-tool score: 42 (ranging 35 - 72).
BIM operations: walls, slabs, columns, windows, doors, IFC export/import
Hands-In / Hands-Off bridge control for live FreeCAD GUI sessions. Hands-In uses the TCP bridge (FreeCAD.exe + fc_bridge.py) for live modeling, viewport screenshots, and object inspection. Hands-Off uses FreeCADCmd subprocess. ## Operations - status: bridge connectivity and effective execution mode - set_execution_mode: persist auto | hands_in | hands_off preference - ensure_gui: start/connect FreeCAD bridge if needed - list_objects: object tree for active/target document - screenshot_view: capture 3D viewport PNG (vision loops) - execute_script: run bounded Python in live document context - new_document: create empty document in live GUI ## Examples await freecad_bridge(operation="status") await freecad_bridge(operation="ensure_gui") await freecad_bridge(operation="screenshot_view", width=1920, height=1080) await freecad_bridge(operation="execute_script", script="doc.addObject('Part::Feature','Box').Shape = Part.makeBox(10,10,10)")
CFD workflow: FreeCAD geometry → OpenFOAM mesh + CFX configuration → run simulation → post-process results
Model marketplace integration: search Thingiverse/GrabCAD, download STL/STEP files, cache management
Finite Element Analysis: mesh generation, material assignment, boundary conditions, solver execution
5 of 7 tools (freecad_cfd, freecad_bim, freecad_fem, freecad_fluidx3d, freecad_depot) have ZERO visible input parameters beyond the 'operation' enum. They lack operation-specific parameters (dimensions, materials, solver settings, query terms, etc.).
freecad_model has 30+ parameters, exceeding production baseline of p90=8. Parameter set is overwhelming and invites LLM confusion about which params apply to which operation. Missing documented operation-specific parameter dependencies (e.g., 'gear' operation uses num_teeth, module, pressure_angle_deg; 'toy_car' uses body_length_mm, wheel_radius_mm; these should be clearly scoped per operation).
No tool documents output schemas. LLMs cannot plan downstream calls or extract required fields (e.g., after create_primitive, what fields does the response contain? Is there an object_id for use in downstream fuse/cut operations?). All tools should document return type structure.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 40 | <=2025-11-25 | v2 |
GPU-accelerated CFD via FluidX3D: geometry voxelization, multiphase flow, turbulence modeling, result export
Parametric FreeCAD modeling for agentic CAD workflows. Supports Hands-In (live GUI bridge) and Hands-Off (FreeCADCmd subprocess). Operations: create_primitive, gear, fastener, inspect, clash_check, techdraw, sketch, assembly, generative, heuristic_fillet, inspect_assembly, fuse, cut, common, mirror, extrude, fillet, transform, export, toy_car.
Descriptions for freecad_cfd, freecad_bim, freecad_fem, freecad_fluidx3d, freecad_depot are bare operation lists (15-116 chars) lacking actionable context. They do not explain WHEN to call the tool, WHAT it does, or WHAT HAPPENS. Rubric baseline: 194 chars avg, 10-1024 range. These fail the <20 char rule: description score capped at 0-20.
No tool includes error handling guidance. freecad_bridge and freecad_model execute arbitrary Python scripts and model operations, failures are common (invalid script syntax, mesh generation timeout, CFD solver divergence). Tools must return actionable errors: 'Mesh generation failed: domain too small. Increase domain size or reduce element count.' Currently, error responses are unguided.
freecad_bridge and freecad_model expose script/code execution as tool parameters. While input validation is present in validate_bridge_script(), no evidence of injection protection (SQL, command, path traversal). LLMs can be tricked into passing malicious code. Sanitize and validate all code input; sandbox execution context; document security boundaries.
Tool naming inconsistency. 'freecad_bridge' and 'freecad_model' are domain-prefixed nouns. 'freecad_cfd', 'freecad_bim', 'freecad_fem', 'freecad_fluidx3d', 'freecad_depot' lack action verbs (get_, create_, run_, etc.). Should be 'run_cfd_simulation', 'create_bim_wall', 'setup_fem_analysis', 'run_fluidx3d', 'search_depot'. Inconsistent naming confuses LLMs when discriminating tools.
freecad_model parameter 'params' is a bare object with no schema documentation. What keys does it expect? Are all keys required? What happens if params is null? Rubric requires: 'Describe the expected format, range, and allowed values directly in the parameter description.' This is missing.
freecad_model 'placement' parameter is documented as 'Placement dict: x,y,z,rx,ry,rz in mm/deg' but has no schema validation. LLMs may pass {'x':100} (incomplete) or {'x':'100'} (wrong type). Use formal schema with required keys and strict typing.
freecad_model 'object_names' and 'parts' parameters are arrays but lack item schema details. What structure do 'parts' items expect? The description says 'Primitive specs for Hands-Off boolean ops' but doesn't enumerate required/optional fields. LLMs will guess.