Skip to main content
Glama

render_start

Starts rendering queued jobs, or all jobs when none are specified. Set wait to true to block until completion and return output files, or false to return immediately and poll status.

Instructions

Start rendering queued jobs (all if job_ids omitted). wait=true blocks until done and returns output files; wait=false returns immediately (poll with render_status).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNo
job_idsNo
timeoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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 does disclose the key traits: blocking vs non-blocking execution and that output files come back on the blocking path. It says nothing about what happens when the blocking call times out (default 3600s), whether jobs are consumed/removed from the queue, or any permission requirements.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with no filler; the default-scope qualifier is parenthesized inline and the blocking/non-blocking split is presented as a direct contrast.

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?

There is no output schema and no annotations, so the description must cover behavior and returns — it does for the success path (output files) but leaves timeout semantics and post-start job state unspecified. That gap matters for a tool whose default mode blocks for up to an hour.

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 explains job_ids (omitted = all jobs) and both values of wait, but the third parameter, timeout, is never mentioned, leaving an agent to guess it is a blocking-call deadline.

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?

Opens with a specific verb+resource ("Start rendering queued jobs") and immediately states the default scope ("all if job_ids omitted"). It also names render_status so an agent can separate this from the polling sibling 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 a clear decision rule for the main fork: wait=true blocks and yields output files, wait=false returns immediately and should be followed by render_status. It does not advise when to prefer blocking over polling (e.g. long batches) or mention the timeout's role.

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