No user-submitted related servers found.
Scored across 113 tools
Most tools target clearly distinct resources or lifecycle stages (mesh editing, project parameters, jobs, sessions, results, studies), and descriptions often clarify boundaries. However, with 113 tools there are overlapping clusters such as mdpa_create_structured_mesh / mdpa_create_geometry_mesh / mesh_generate_gmsh / mesh_import, add_boundary_condition vs project_add_process, and create_materials vs materials_set_property, which can cause misselection.
The set uses snake_case and domain-prefixed families (mdpa_*, project_*, job_*, session_*, results_*, study_*), which is readable. But it mixes verb-first names like create_project and add_output_process with noun-first names like materials_get, results_list, mdpa_inspect, and job_status, so the naming convention is not fully predictable.
113 tools is far beyond a manageable, well-scoped surface for an agent to reliably discover and choose from. Even for a broad domain such as Kratos simulation setup and execution, this count indicates an extreme mismatch rather than a focused set.
The surface is extremely comprehensive: installation, documentation, variable/process/solver discovery, templates, project and materials creation/editing, mesh generation/import/export/editing/validation, simulation runs, checkpoints, interactive sessions, results analysis, rendering, and studies are all covered. Obvious lifecycle operations have corresponding tools, leaving few dead ends.