Skip to main content
Glama

log_phases

Destructive

Inspect executed LAMMPS phases in an existing log, extract fixes, groups, timestep, units, and normalization, and use them as thermo phase selectors without hand-counting block indices; read-only.

Instructions

Inspect actual executed LAMMPS phases in an existing log, including fixes, groups, time step, units and normalization. Use those facts as thermo phase selectors; repeated runs/headers need no hand-counted block index. Reads existing data only.

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": "log_phases"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/5

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

The description states 'Reads existing data only' and frames the tool as inspection, while annotations declare readOnlyHint=false and destructiveHint=true. This is an explicit conflict about the tool's safety profile, leaving the agent unable to tell whether calling it can mutate data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences with the purpose front-loaded, so it is not bloated. It leans on unexplained internal jargon ('thermo phase selectors', 'hand-counted block index') that an unfamiliar agent cannot decode.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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, but for a tool with zero parameter documentation the description leaves both required arguments opaque. Combined with the unresolved read-versus-destructive ambiguity, an agent lacks what it needs to invoke this confidently.

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% and the description never names or explains either required parameter ('path', 'task_id'). At best, 'in an existing log' loosely hints that path points to a log, but task_id is 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?

Names a specific verb and resource: inspecting executed LAMMPS phases in an existing log, and enumerates what is surfaced (fixes, groups, time step, units, normalization). It does not distinguish itself from plausible siblings such as run_log or lammps_input_review, so it stops short of 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 Guidelines3/5

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

It gives downstream usage guidance ('use those facts as thermo phase selectors') and clarifies that repeated runs/headers need no hand-counted block index, which is a useful usage note. However, it never says when to choose this over alternatives or what prerequisites exist beyond 'an existing log'.

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