ls-dyna-mcp

Overview Schema Source Related Servers Discussions Admin

get_solve_status

Check LS-DYNA solve status safely while Mechanical is busy: returns 'Solving' during active solves, then the completed result, plus solver messages and working directory.

Instructions

Solution status, Mechanical messages and the solver working directory. While a solve started by solve_analysis is running, answers 'Solving' without touching Mechanical (which is busy), then returns that solve's result once. Args: analysis_index

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_solve_status"
  }
}

Input Schema

Name	Required	Description	Default
`analysis_index`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.9.2Oct 24, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that the tool avoids touching Mechanical while it is busy and returns the solve result only once. It still leaves out error behavior and whether the operation is strictly read-only, but it adds meaningful non-schema behavior.

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?

The description is short and front-loads the returned information before the behavioral caveat. The single 'Args:' line is terse but does not clutter the definition.

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 values need not be explained, and the description covers the key busy-Mechanical behavior. However, for a one-parameter tool with 0% schema coverage and no annotations, the unexplained analysis_index leaves a meaningful gap.

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 only parameter, analysis_index, has 0% schema description coverage and is mentioned only as 'Args: analysis_index'. The description does not explain what the index refers to, how it should be chosen, or what the default 0 means.

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?

The description clearly states that the tool returns solution status, Mechanical messages, and the solver working directory. It does not explicitly distinguish itself from nearby siblings such as get_solution_information or get_run_progress, so it misses the top score.

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?

It gives a clear usage context: while a solve started by solve_analysis is running, the tool answers 'Solving' without touching busy Mechanical, then returns that solve's result once. It does not name when to use alternatives or explicitly say when not to use this tool.

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

Deploy Server