Model Context Protocol server for LUSAS Modeller, providing tools to interact with LUSAS finite element analysis software via COM interface
LUSAS MCP has significant definition quality gaps. Tool names are verb-based (get_, create_, sweep_, select) which is good, but descriptions are minimal (10-50 chars, well below the 194-char baseline). Most critically, input schemas lack proper type definitions and parameter descriptions. The GeomObject class is defined but parameter descriptions are sparse. Error handling is absent, tools return plain strings rather than structured error responses. No output schemas are documented. The server exposes Windows COM internals without abstraction, forcing agents to understand LUSAS-specific concepts.
Creates geometry objects (points, lines, arcs, surfaces, volumes) in LUSAS modeller from coordinate data.
Retrieves all geometry objects (points, lines, surfaces, volumes) from the current LUSAS model.
Retrieves all lines from the current LUSAS model.
Retrieves all points from the current LUSAS model.
Retrieves all surfaces from the current LUSAS model.
Gets the units of the current model.
Retrieves all volumes from the current LUSAS model.
Descriptions are too short (10-50 chars vs 194-char baseline). Most lack context for LLM tool selection. E.g., 'Retrieves all points from the current LUSAS model' (50 chars) does not explain WHEN to call it or what structure is returned.
Parameter descriptions are missing or minimal. 'sweepVector' is described as 'Vector for sweep operation [x, y, z]' but lacks units, constraints, or format guidance. 'objectType' in select() has no enum constraint, LLM must guess valid values.
No output schemas documented. Tools return plain strings ('Points created successfully with IDs...') instead of structured JSON. LLM cannot extract IDs for downstream tool calls. Violates response-shaper pattern.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | <=2025-11-25 | v2 |
Selects geometry objects in LUSAS modeller by their IDs.
Sweeps lines in LUSAS modeller to create surfaces or volumes.
Sweeps points in LUSAS modeller to create lines or surfaces.
Sweeps surfaces in LUSAS modeller to create volumes.
Error handling is absent. Tools return plain error strings ('Error: Cannot connect...') with no recovery guidance. LLM cannot determine if error is retryable, user-fixable, or fatal. No actionable error messages.
Parameter 'objectType' in select() lacks enum constraint. Description says 'e.g., Point, Line, Surface, Volume' but does not enforce valid values. LLM may pass invalid types, causing silent failures.