No user-submitted related servers found.
Scored across 73 tools
The set has many overlapping clusters: simulation_submit, simulation_deck_run, simulation_case_create, simulation_validate, simulation_results, simulation_compare, and simulation_snapshot are hard to distinguish without reading deep descriptions, and several import tools (dataset_import, dataset_import_snapshot, geodata_import, eclipse_import, grid_import, seismic_import, seismic_source_import) have blurred boundaries. Many tools also have descriptions that are just the tool name (properties_reference, fault_create, properties_assign, scenarios_run, seismic_generate), forcing the agent to guess.
Most names are snake_case, but the convention mixes verb_noun (create, list, inspect, import), noun_verb (fault_create, properties_assign, volumetrics_calculate, seismic_generate), and bare nouns (diagnostics, start, properties_reference). It remains readable, but the inconsistent ordering and vague standalone names reduce predictability.
At 73 tools, the surface is far beyond a well-scoped set and includes many highly specialized operations plus multiple workflow/job/scene management tools. The breadth is excessive even for a broad reservoir-modeling platform, making discovery and correct selection difficult.
The surface covers import, QC, model building, property modeling, volumetrics, simulation, uncertainty, ensembles, export, visualization, and job/project management, so core domain workflows are broadly represented. Gaps are mostly lifecycle operations such as delete/update for projects, workflows, or artifacts, and some tools lack enough detail to assess their coverage.