Skip to main content
Glama
Sign In
HydroStar MCP

HydroStar MCP

by lightninnng
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

case_status

Read-only

Retrieves persisted case state, step timings, log paths, mesh checks and result summaries so you can track progress and verify hydrodynamic analysis quality for a given case ID.

Instructions

Read persisted state, step timings, log paths, mesh checks and result summaries.

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": "case_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, and the description adds value by naming the categories of data surfaced (timings, log paths, mesh checks, result summaries). It says nothing about behavior for cases that haven't started, permissions, or failure modes, but with annotations carrying the safety profile a 3 is appropriate.

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?

A single front-loaded sentence listing the returned data with zero filler. It is a verbless-leaning fragment, but every word carries information.

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

Completeness3/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-shape explanation isn't required, yet the description spends its content enumerating returns anyway. It omits the relationship to sibling tools and how to obtain a valid case_id, which leaves the definition adequate but incomplete for a lifecycle-status tool.

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

Parameters2/5

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

The schema has 0% description coverage for the single required case_id parameter, and the description never mentions it or explains its format/source (e.g., value returned by plan_case or make_reference_case). With only one parameter the burden is small, but the description does nothing to compensate for the schema gap.

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

Purpose4/5

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

States a specific verb ('Read') and enumerates the concrete data returned (persisted state, step timings, log paths, mesh checks, result summaries), which together with the name case_status identifies this as a read-only status lookup. It does not explicitly say 'for a given case' nor contrast with siblings like inspect_environment or read_rao, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to call this versus the many sibling lifecycle tools (plan_case, start_case, cancel_case, inspect_environment). An agent must infer that this is the post-hoc inspection tool from the name alone.

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