Skip to main content
Glama

lammps_reference

Read-onlyIdempotent

Fetches cached official LAMMPS syntax, examples, and restrictions for a specified command and engine version, with pagination, to guide writing or repairing native input files.

Instructions

Read cached official Syntax, Examples and Restrictions for the actual engine version, e.g. command='compute pe/atom', engine_version='28Mar2023'. Follow next_offset until more=false. Fetches only the requested official LAMMPS page and retains its source/hash; use before writing or repairing native inputs.

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": {
      "command": "<command>",
      "engine_version": "<engine_version>"
    },
    "name": "lammps_reference"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
commandYes
engine_versionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: results come from cache, only the requested page is fetched, source and hash are retained, and pagination is driven by next_offset until more=false. It omits failure behavior for unknown commands or versions, which keeps it from a 5.

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 dense, front-loaded sentences with no filler; purpose comes first, then the pagination contract, then the usage constraint. The inline examples make the first sentence slightly heavy but each carries useful information.

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?

An output schema exists, so return values need not be spelled out, and the description still surfaces the key response signals (more flag, next_offset). Combined with the caching/provenance notes, it is sufficient to call correctly, though limit/offset input semantics remain underspecified.

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

Parameters3/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 compensate, and it only partly does: it supplies concrete examples for command ('compute pe/atom') and engine_version ('28Mar2023'). The limit and offset parameters are never explained — pagination is described via 'next_offset', an output field rather than the input param — leaving half the parameters ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Read) and a precisely scoped resource: cached official Syntax, Examples and Restrictions for a given engine version. The scope qualifier ('for the actual engine version') makes it clearly distinct from a general docs lookup or from the sibling input-review tool.

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?

Gives a clear use context with 'use before writing or repairing native inputs', which tells the agent this is a pre-authoring lookup. It stops short of naming an alternative or stating when not to use it (e.g. vs. lammps_input_review), so it lands at 4 rather than 5.

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