Skip to main content
Glama
Sign In
ls-dyna-mcp

ls-dyna-mcp

by codersag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_restart_setup

Validate an LS-DYNA restart before solving by checking documented restart rules and confirming the required files (d3dump or d3full) exist in the prior run directory.

Instructions

Validate a Simple / Small / Full restart before solving: the documented rules (e.g. a small restart is impossible for a serial single-precision solution; a small restart needs a later end time) and, if directory (the earlier run's folder) is given, whether the restart files it needs are really there (d3dump for simple/small, d3full for full). Times of 0 are treated as unknown. Args: restart_type, solver_precision (single|double), processing_type (SMP|MPP), number_of_cores, previous_end_time, new_end_time, directory

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": {
      "restart_type": "<restart_type>"
    },
    "name": "check_restart_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryNo
new_end_timeNo
restart_typeYes
number_of_coresNo
processing_typeNoSMP
solver_precisionNodouble
previous_end_timeNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.2

TDQS

A4/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 behavioral burden and does well: it discloses the validation rules, required restart files by type (d3dump vs d3full), and that time values of 0 are treated as unknown. It never explicitly says the tool is read-only or has no side effects, but the 'validate/check' framing strongly implies that.

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 definition is front-loaded and dense, with most sentences contributing concrete rules or parameter meaning. The trailing 'Args:' list partly repeats content already implied earlier, but it usefully enumerates all parameters given the bare schema titles.

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?

For a 7-parameter validation tool with no annotations but an output schema, the description covers the essential validation logic, file checks, and parameter meanings. It could add an explicit side-effect profile, but nothing critical for correct invocation is missing.

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

Parameters4/5

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

Despite 0% schema description coverage, the description names all seven parameters and adds meaningful semantics: 'directory' is the earlier run's folder, solver_precision is single|double, processing_type is SMP|MPP, restart_type values are Simple/Small/Full, and 0 times are unknown. It leaves number_of_cores and the exact previous/new end-time distinction relatively bare, so not a 5.

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 states a specific verb (validate) and resource (restart setup), and details the concrete rules and file checks involved for Simple/Small/Full restarts. It does not explicitly distinguish itself from related siblings such as presolve_check or list_restart_files, which keeps it from 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 Guidelines4/5

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

The phrase 'before solving' gives clear timing context, and it explains the conditional behavior when 'directory' is supplied. It does not name alternatives or state when not to use it, but the usage context is clear enough for an agent.

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