No user-submitted related servers found.
Scored across 9 tools
Each tool maps to a distinct stage of the FEKO workflow (environment, CAD scripting, model creation, solving, status, artifacts, results, API docs). The only mild overlap is between create_preliminary_model and run_cad_script, both of which produce CAD models, but their descriptions draw a clear line between a canned parameterised example and arbitrary Lua execution.
All nine tools follow a clean verb_noun convention (get_environment, run_cad_script, create_preliminary_model, start_solver, get_job_status, read_result_text, etc.). No mixing of camelCase or vague verb styles.
Nine tools is well-scoped for a simulation pipeline covering discovery, model building, solve, monitoring, and result extraction. Each tool earns its place with no filler.
The surface covers the full lifecycle from environment discovery to reading results and API reference, with polling-based status for async solves. Minor gaps like job cancellation/cleanup or solver configuration tweaking exist but are workaroundable via Lua scripts.