HydroStar MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HSTAR_PATH7 | No | Path to the local HydroStar 8.2.0 installation directory (e.g. C:\path\to\Hstar4Experts\v8.2.0), used for re-running solver calculations. Offline planning, input export and viewing published results work without it. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_environmentA | Locate solver executables and supported capabilities; does not claim license availability. |
| inspect_geometry_sourceC | Read supported source routes or inspect a source inside HS_SOURCE_ROOT. |
| build_geometryA | Build an independently checked, provenance-preserving wetted HST bundle. CAD and section data use an isolated OpenCASCADE/Gmsh process. Drawing inputs produce a metric tracing workspace. Use case_geometry from accepted output in prepare_case, with explicit mass, CG, inertia and the desired wave conditions. Choose panel_layout by topology: ring_bands for coaxial columns, station_bands for smooth x-axis lofts, polygon_blocks for a prismatic through opening, or quad_dominant for general CAD patches. Quality limits are explicit and frozen. |
| list_reference_formsB | Read built-in source-informed hull families, feature allocation and citations. |
| make_reference_caseB | Create a reviewable typed recipe from public scalar references, without writes. Returns source comparison and a full plan. Generate/prepare the returned config using the normal gates; benchmark equivalence is evaluated separately. |
| plan_caseB | Validate semantic input, estimate panel counts and screen wavelength before writing files. |
| generate_inputsB | Export reviewable parametric MRI/HST (or imported HST), RDF, MCN and RAO. This works without a HydroStar license. The generated status means input export only; use prepare_case before attempting any calculation. |
| prepare_caseB | Generate geometry/RDF/MCN/RAO and check a fresh mesh before the motion solve. If planning requires confirmation, call again with that plan's token only after human agreement. Measured mesh warnings require another review before start_case. |
| start_caseA | Start a previously prepared case asynchronously. Poll case_status for results. Supply the measured-mesh confirmation token only after human review when requested. Input modification invalidates preparation. Each case may be solved once. |
| case_statusB | Read persisted state, step timings, log paths, mesh checks and result summaries. |
| cancel_caseB | Request cancellation of this service's queued or active job and its solver process tree. |
| read_raoC | Read complete validated RAO arrays, original amplitude unit and phase values (degrees). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The tools mostly map to distinct stages of the HydroStar workflow, from environment/geometry inspection through case preparation and result reading. A few boundaries could still be confused, especially generate_inputs versus prepare_case and make_reference_case versus plan_case, though the descriptions provide clarifying context.
Most tool names follow a consistent snake_case verb_noun pattern such as inspect_environment, build_geometry, plan_case, and read_rao. The main deviation is case_status, which lacks a verb and breaks the otherwise predictable pattern.
Twelve tools are well-scoped for a multi-stage engineering workflow involving inspection, geometry building, planning, execution, monitoring, and results retrieval. Each tool appears to earn its place without obvious redundancy or excessive breadth.
The surface covers the core lifecycle from environment inspection and geometry setup through case execution, cancellation, and RAO retrieval. Minor gaps exist around listing existing cases or cleaning up completed cases, which agents may need to work around.