Skip to main content
Glama

data_inspect

Read-onlyIdempotent

Inspect LAMMPS thermo or per-atom trajectory files to verify column identities, frame counts, and dataset structure before analysis.

Instructions

Inspect actual LAMMPS thermo or per-atom trajectory data. Columns, frame counts and identities come from files.

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>",
      "kind": "<kind>"
    },
    "name": "data_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
pathYes
task_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds that columns, frame counts, and identities come from the files themselves, which usefully signals the result depends on file contents rather than caller input, but says nothing about errors on malformed files or cost of large trajectories.

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?

Two short sentences, front-loaded with the action and its object, with no filler. The second sentence earns its place by clarifying that structure is derived from files.

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 described, but with three required parameters at 0% schema coverage the definition should explain what each parameter denotes. It leaves too much for an agent to guess.

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 coverage is 0% and the description does not explain path, kind, or task_id beyond indirectly hinting that 'thermo or per-atom' may be the kind values. An agent gets little help on what path should point to or what task_id scopes.

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?

States a specific verb and resource: 'Inspect actual LAMMPS thermo or per-atom trajectory data.' This distinguishes it from a legacy/metadata inspector, though it does not name a sibling explicitly.

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

Usage Guidelines2/5

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

No guidance on when to prefer this over legacy_inspect or other inspection tools, and no prerequisites such as requiring a task_id or an already-registered artifact. The word 'actual' implies inspecting real data rather than descriptors, but this is left implicit.

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