Skip to main content
Glama
JasmyLab-JANCTION

JANCTION Render

by JasmyLab-JANCTION
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_download

Read-onlyIdempotent

Download a render job's files locally and return their paths. Choose only=mp4 for just the video, frames for images, or wait_seconds to wait before downloading.

Instructions

Download a job's files to out_dir (default ~/janction-render/<job_id>) and return the local paths. only picks the files: 'all' (default), 'mp4' (just the video; use it when the user wants the video, to skip hundreds of frames), 'frames', 'sheet' or 'output'. wait_seconds > 0 first waits that long for the job to finish.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
onlyNo'all' (every frame plus output.mp4 / sheet.png) | 'mp4' | 'frames' | 'sheet' | 'output' (the MP4 or the sheet only).all
job_idYesThe job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs; in render_status, leave it empty to list them.
out_dirNoLocal folder to save the files in (default ~/janction-render/<job_id>).
wait_secondsNoWait up to this many seconds for the job to finish before downloading (0 = do not wait).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.119
    • addedInput schema / properties / job_id / description
      Added value: +"The job_id returned by render_preview or render_final (j_...; a long final split into parts is b_...). Only this key's jobs; in render_status, leave it empty to list them."
    • addedInput schema / properties / only / description
      Added value: +"'all' (every frame plus output.mp4 / sheet.png) | 'mp4' | 'frames' | 'sheet' | 'output' (the MP4 or the sheet only)."
    • addedInput schema / properties / out_dir / description
      Added value: +"Local folder to save the files in (default ~/janction-render/<job_id>)."
    • addedInput schema / properties / wait_seconds / description
      Added value: +"Wait up to this many seconds for the job to finish before downloading (0 = do not wait)."
  2. Changed1 schema field changedv0.2.2
    • addedInput schema / properties / only
      Added value: +{
+  "default": "all",
+  "title": "Only",
+  "type": "string"
+}
  3. First observedv0.2.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds context the annotations cannot: artifacts are written to a local directory (~/janction-render/<job_id> by default), local paths are returned, and a positive wait_seconds blocks until the job finishes. It does not describe behavior when the job is still unfinished with wait_seconds=0, or download size/limits.

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?

Roughly three compact sentences, front-loaded with the action and destination before the option list; every sentence carries information. Minor awkwardness in the 'only picks the files' phrasing and the inline enumeration, but no filler.

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 not be spelled out, and the schema plus annotations cover parameters and safety. What remains thin is the unfinished-job case (behavior when wait_seconds=0 and the job is not done) — otherwise the definition is sufficient to call the tool correctly.

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 100%, so all four parameters are already documented — the baseline is 3. The description mostly restates the enum values and the out_dir/wait_seconds defaults, adding only the rationale for 'mp4' ('to skip hundreds of frames'), which is a modest value-add beyond the schema.

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+resource ('Download a job's files') plus the destination ('out_dir, default ~/janction-render/<job_id>') and the return ('local paths'). It is unambiguous among siblings such as render_preview, render_final and render_status, which produce or inspect jobs rather than retrieve their artifacts.

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 selection guidance for the 'only' mode, including the condition for the most important case ('mp4' — use when the user wants the video, to skip hundreds of frames), and explains the wait_seconds timing tradeoff. It does not, however, state when to prefer this tool over render_status/render_preview for checking job state, so there is no explicit exclusion.

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

Deploy Server

Other Tools