Skip to main content
Glama
Sign In
HydroStar MCP

HydroStar MCP

by lightninnng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

start_case

Launch a prepared hydrodynamic case asynchronously and poll case_status for results; provide the confirmation token only after human review when required.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "case_id": "<case_id>"
    },
    "name": "start_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes
confirmation_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does well: it discloses asynchronous execution, the required polling step, that input modification invalidates preparation, and that 'Each case may be solved once' (a one-shot irreversibility constraint). It does not state what happens on a second start attempt, needed permissions, or the compute cost/side effects of solving.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences with the core action and the polling follow-up front-loaded; every sentence adds a distinct constraint. Minor ambiguity ('when requested' by whom/where) keeps it just below top marks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be described, and the description covers async semantics, polling, and the one-shot constraint. Gaps remain around failure modes (starting an unprepared or already-started case) and the source of the confirmation token, which matter for a tool with no annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate for both parameters. It gives partial meaning for confirmation_token (a 'measured-mesh confirmation token' gated on human review when requested) but never explains case_id, the required parameter, or where the token originates and what 'requested' means. Partial compensation only.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Start') plus resource ('case') plus a precondition ('previously prepared') that distinguishes it from prepare_case, plan_case, and make_reference_case in the sibling list. An agent can identify the correct tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to the sibling case_status for results via polling, and constrains the confirmation_token to 'only after human review when requested'. It implies the precondition (case must already be prepared) but does not explicitly state what to do if the case is not prepared or what alternative to use then.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools