No user-submitted related servers found.
Scored across 40 tools
Each tool targets a distinct resource and action, from environment setup, entity listing, case creation, modification, validation, simulation running, job management, to result analysis and graph conversion. Even closely related tools like list_templates and create_project_parameters have clear boundaries, and no two tools appear to do the same thing.
The naming is readable but mixed: many tools use kratos_verb_noun (e.g., kratos_list_applications), while others drop the prefix (list_templates, create_project_parameters) and several use noun_verb (mdpa_inspect, job_status, results_list). This inconsistency across groups reduces coherence, though the pattern is somewhat predictable within each group.
With 40 tools, the server exceeds the rubric's 'too many' threshold of 25+. While the broad Kratos multiphysics domain justifies a large surface, the sheer number feels heavy and could overwhelm agents, even though each tool earns its place.
The tool surface covers the full simulation lifecycle: installation, environment introspection, case scaffolding, parameter modification, validation, mesh generation, running simulations, job monitoring, results extraction, and Flowgraph conversion. Minor gaps exist, such as the lack of a tool to remove or update existing boundary conditions in a ProjectParameters.json, but these are workaroundable by regenerating or editing files directly.