Skip to main content
Glama

job_output

Download a completed Kaggle job's output files to a local directory and clean up ephemeral resources, keeping incomplete runs for resumption.

Instructions

Download a finished job's output files (default: <project_dir>/kaggle_out/<job_id>/).

For ephemeral jobs the kernel and its per-job dataset are then deleted from Kaggle, unless
the run stopped at its time limit (incomplete): then it is kept so a new job can resume it.

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_output"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
dest_dirNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a non-obvious destructive side effect: for ephemeral jobs the kernel and per-job dataset are deleted from Kaggle after download, with the time-limit exception explained. It still omits whether existing files at dest_dir are overwritten and what happens for non-ephemeral jobs.

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 destination default before the deletion caveat. No filler, though the parenthetical path and the nested 'unless…then' clause make the second sentence slightly harder to parse than necessary.

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 return values need no explanation, and the most dangerous behavior (Kaggle-side deletion) is disclosed. Remaining gaps — behavior when the job is not yet finished and dest_dir handling — are modest for a two-parameter download 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 dest_dir's default location, which is genuinely useful beyond the schema. But it never says how a caller-supplied dest_dir is interpreted (created? absolute vs relative?) or what form job_id 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?

States a concrete verb and resource — 'download a finished job's output files' — plus the default destination path, which lets an agent separate it from job_logs and job_status. The word 'finished' implicitly scopes it against submit_job, though no sibling is named explicitly.

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?

The precondition 'finished job' implies when the tool may be called, and the ephemeral-job clause implies a follow-on consequence. However, nothing tells the agent to check job_status first or what to do if the job is still running, and no alternative tool is named.

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