Skip to main content
Glama

trajectory_correlate

Read-onlyIdempotent

Link saved trajectory frames to exact thermo samples by Step and recorded Time, preserving duplicate-step ambiguity and returning matching rows for plots and structural previews.

Instructions

Link saved trajectory frames to exact thermo samples by Step and recorded Time, optionally selecting an executed phase (fix_id/style/group/marker/run_index/timestep). Preserve duplicate-step ambiguity; no interpolation or step*current-dt inference. Returns frame/cell/atom-type facts and actual matching rows for plots and structural previews.

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>",
      "trajectory": "<trajectory>",
      "log": "<log>"
    },
    "name": "trajectory_correlate"
  }
}

Input Schema

NameRequiredDescriptionDefault
logYes
phaseNo
task_idYes
trajectoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, and the description adds real semantics on top: duplicate-step ambiguity is deliberately preserved (no deduplication), and no interpolation or step*current-dt inference is performed. That is a meaningful disclosure of how matching is constrained, though it says nothing about scaling, size limits, or error behavior on missing phases.

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 sentences with no filler, front-loaded with the core join operation and followed by the caveats and return content. It is jargon-heavy but each clause adds information an agent needs.

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 the description need not detail return values, yet it still sketches frame/cell/atom-type facts and matching rows. For a four-parameter join tool with a free-form phase object, the main gap is the unexplained task_id and the absence of guidance on what happens when no matching rows or phases exist.

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 carry the parameter burden. It substantially illuminates the opaque free-form 'phase' object by listing fix_id/style/group/marker/run_index/timestep, but task_id is never mentioned and log/trajectory are only implied ('thermo samples', 'saved frames'), leaving the join inputs loosely specified.

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 gives a specific verb and paired resources: 'Link saved trajectory frames to exact thermo samples by Step and recorded Time.' That is concrete enough to distinguish from a log-listing or data-inspection tool, but it never names a sibling or explicitly states which alternative to prefer.

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 only implied: the description mentions opting into an 'executed phase' and warns against interpolation and step*current-dt inference, which hints at when this is the right tool. There is no explicit when-to-use/when-not guidance or comparison to alternatives such as log_phases.

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