Skip to main content
Glama

get_logs

Retrieve the last configured number of stdout/stderr log lines from a GPU training run to inspect errors, monitor progress, and diagnose failures.

Instructions

Return the last tail lines of a run's stdout/stderr log.

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_name": "<run_name>"
    },
    "name": "get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
tailNo
run_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: both streams (stdout/stderr) are returned and the result is truncated to a trailing window. It says nothing about what happens if the run doesn't exist, whether logs are persisted across restarts, or how large logs are handled.

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?

A single sentence with no filler, and the most important fact (truncated tail of the log) is front-loaded. Minor noise comes from the doubled backticks, an RST artifact rather than intentional formatting.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (two parameters, one required) and an output schema exists, so return values need not be described. Still, with zero annotation coverage the description should say more about the required run_name and error conditions to be fully self-sufficient.

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. It does explain `tail` as a count of trailing lines, which adds meaning beyond the bare integer type, but it never mentions the required `run_name` parameter or what form a run name takes.

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 names a specific verb ("Return") and resource ("a run's stdout/stderr log") and states the scope ("the last tail lines"), which distinguishes it from siblings like get_metrics and get_run_status. It does not explicitly name an alternative, 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 Guidelines2/5

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

There is no when-to-use guidance, no condition that selects this over get_metrics or get_run_status, and no mention of prerequisites such as the run having finished or still being active. Usage is only inferable from the purpose statement itself.

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