Skip to main content
Glama

lammps_input_review

Read-onlyIdempotent

Reviews an existing LAMMPS input for known compute-current mistakes, reporting line numbers, content hash, and official references so you can verify issues on accounted HPC without rewriting scripts.

Instructions

Read an existing native input and report known compute-current mistakes with line numbers, content hash and official references. Read dependencies for dynamic control flow, then verify on accounted HPC. No script rewriting or physics execution.

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": {
      "task_id": "<task_id>",
      "path": "<path>"
    },
    "name": "lammps_input_review"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
task_idYes
engine_versionNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description still adds real behavioral context: it reports line numbers, a content hash and official references, follows dependency chains for dynamic control flow, and explicitly does not rewrite scripts or execute physics. The only shortfall is the vague reference to verifying 'on accounted HPC', which does not clarify what that entails for the caller.

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?

Three short sentences with the purpose and output details front-loaded, and no filler. The middle sentence about dependencies and HPC verification is terser than it should be and reads as compressed jargon rather than precise instruction.

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 the description need not explain return values, and it reasonably stays focused on purpose and limits. However, for a three-parameter tool with zero schema coverage, leaving task_id and engine_version entirely unexplained makes the definition incomplete for correct invocation.

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?

Schema description coverage is 0%, so the description must carry the burden, and it does not: neither task_id nor engine_version is mentioned, and only 'Read an existing native input' loosely gestures at the path parameter. With a required task_id unexplained, the schema gap is left entirely unaddressed.

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 names a specific verb and resource ('Read an existing native input') and enumerates concrete outputs ('known compute-current mistakes with line numbers, content hash and official references'), which is far more specific than a restatement of the name. It does not, however, explicitly distinguish itself from the sibling lammps_reference tool, despite referencing 'official references' that likely live there.

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

Usage Guidelines3/5

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

Usage is implied by the workflow sentence ('Read dependencies for dynamic control flow, then verify on accounted HPC') and bounded by exclusions ('No script rewriting or physics execution'), so an agent can infer this is a review-only pass. But there is no explicit when-to-use versus alternatives such as lammps_reference, and 'accounted HPC' is undefined jargon that leaves the agent guessing about prerequisites.

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