Skip to main content
Glama

job_logs

Fetch stdout and stderr logs for a Kaggle job’s latest run, with an optional tail character limit, to diagnose failures and review completed output.

Instructions

stdout/stderr of a job's latest run (last tail_chars characters; 0 = all).

Kaggle usually publishes the log only after the run finishes.

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": {
      "job_id": "<job_id>"
    },
    "name": "job_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
tail_charsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden and adds useful behavior: it returns only the last tail_chars characters and that logs usually appear only after run completion, which sets latency expectations. It still omits whether a missing/queued log errors or returns empty, and permission or retention behavior, so it is partial rather than rich.

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 returned resource and its truncation rule, then the publish-timing caveat. Minimal waste, though the phrasing 'last tail_chars characters' is slightly cramped and parentheses carry key semantics.

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?

An output schema exists, so return-value explanation is not required, and the description covers truncation and timing well. It remains thin on error/empty behavior for a job that hasn't produced logs and on the job_id parameter, which matters for a low-coverage 2-parameter tool.

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_chars semantics (last N characters, 0 = all), which is genuinely beyond the schema's bare default of 8000. However, job_id gets no added meaning (e.g., format or where to obtain it), so half the parameters remain semantically bare.

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 the specific resource and scope: stdout/stderr of a job's latest run, which clearly distinguishes it from siblings like job_output and job_status (which would return artifacts and state rather than logs). It doesn't explicitly contrast with those siblings by name, so it falls 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?

Usage is implied by the resource description (use this when you need the job's console output), and the note about logs only being published after the run finishes implies a when-not condition. However, there is no explicit statement of when to prefer job_output or job_status instead, so guidance is only partially there.

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