Skip to main content
Glama

run_log

Read-onlyIdempotent

Read a bounded remote job log through the persistent queue to inspect run progress and thermo output without downloading the full trajectory.

Instructions

Read a bounded remote job log through the persistent queue; no full trajectory download.

path is relative to the run directory. offset=None reads the current tail; an explicit byte offset reads a page. Returns operation_id; operation_get returns text, byte range, file size, modification time and complete thermo rows when their header is present. Continue from next_offset. Read physical time units from the native input. A log observation does not declare scientific completion.

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": {
      "run_id": "<run_id>",
      "op_id": "<op_id>"
    },
    "name": "run_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNolog.lammps
limitNo
op_idYes
offsetNo
run_idYes

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 cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds real behavior: reads go through a persistent queue and return an operation_id rather than content, so a follow-up operation_get is required, plus the caution that a log observation does not declare scientific completion.

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?

Dense and front-loaded, with the core read semantics before the follow-up and continuation details. A few sentences are compressed to the point of opacity, notably 'Read physical time units from the native input', which costs clarity rather than saving space.

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?

With an output schema present, the description needn't spell out return values, yet it usefully explains that operation_get supplies text, byte range, size, mtime and thermo rows. The main remaining gap is the unexplained required op_id parameter and limit semantics, both of which matter for a first correct call.

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 explains path (relative to the run directory) and offset (None = tail, explicit byte offset = page), but leaves limit (default 65536) and the required op_id unexplained, and op_id is a required parameter whose origin is unclear.

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 and resource with scope: 'Read a bounded remote job log through the persistent queue; no full trajectory download.' It also distinguishes the tool from operation_get, which is named as the consumer of the returned operation_id, so an agent can separate page-read from result-fetch without opening either schema.

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 concrete operating guidance: offset=None reads the current tail, an explicit byte offset reads a page, and you continue from next_offset. It also implicitly excludes full-trajectory retrieval. What it lacks is an explicit statement of when to prefer this over siblings such as log_phases or file_read.

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