MCP server for nuclear fusion experimental databases (LHD, MAST, Alcator C-Mod)
Strong foundation with 8 well-named tools following verb_noun convention (list_, search_, get_, describe_, download_). All tools have descriptions (avg 150 chars, within 10-1024 baseline). Input schemas are complete with typed properties and required fields. However, output schemas are entirely undocumented, LLMs cannot predict response structure for planning. Parameter descriptions are present but lack format constraints (e.g., date-time format stated but no validation guidance). Error handling is absent from visible code. One tool (download_signal) is WRITE-class but lacks confirmation/dry-run pattern. No tool annotations (readOnlyHint/destructiveHint) despite MCP support.
Get a statistical summary (min, max, mean, std, duration, sample count) of a signal without retrieving the full time series. Use this before get_signal to understand data quality and size.
Download a full-resolution signal to a local file (NPZ by default). Returns the file path and metadata — no data arrays in the response. Use this instead of get_signal when you need the complete time series for Python/matplotlib analysis. Load the result with: data = np.load(path); time = data['time_s']; values = data['data']
Get MHD equilibrium reconstruction data for a plasma shot (if available). Returns flux surfaces, safety factor profile, and geometric parameters.
Get full metadata for a specific plasma shot. shot_id format: '{device_id}:{native_shot_id}', e.g. 'cmod:1120815012', 'mast:30420', 'lhd:184255'.
Retrieve a time-series signal from a plasma shot. Returns time axis (seconds) and data values. Large signals are automatically downsampled to max_samples points. Use describe_signal first to check signal quality.
Output schemas completely undocumented. LLMs cannot predict response structure (fields, types, nesting) for downstream planning or field extraction. Violates pattern:tool requirement.
download_signal is WRITE-class (creates files) but lacks confirmation/dry-run pattern. Agents cannot preview impact before executing. Violates pattern:confirmation-request.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite MCP SDK support. Agents cannot distinguish safe vs. risky tools without reading descriptions.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | <=2025-11-25 | v2 |
List all supported fusion devices with their capabilities, data sources, and access information.
List available diagnostics (signals) for a device or a specific shot. Use this to discover what data is available before calling get_signal.
Search for plasma shots (discharges) on a given device. Filter by date range, plasma current, density, or duration. Returns a list of matching shots with basic metadata.
Error handling not visible in source. No recovery guidance, error classification, or actionable messages. Agents cannot self-correct on failures.
Parameter descriptions lack format/constraint details. E.g., 'date_from' states 'ISO 8601' but no validation guidance. 'diagnostic' accepts 'canonical or native name' but no enum or pattern provided.