Skip to main content
Glama

render_status

Retrieve status, percent complete, output path, and errors for a single DaVinci Resolve render job or the full render queue.

Instructions

Status of one render job or of the whole queue (status, percent, output path, errors).

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

Input Schema

NameRequiredDescriptionDefault
job_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the returned content (status, percent, output path, errors), which implies a read-only probe and adds real value. It does not state read-only-ness explicitly, nor whether the call blocks, how often to poll, or how errors are surfaced.

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?

A single front-loaded sentence with the scope distinction stated before the parenthetical field list; every clause earns its place with 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?

For a one-parameter read tool with no output schema, enumerating the returned fields and covering both the single-job and whole-queue modes is nearly sufficient. Only polling guidance and error behavior are missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single optional job_id at 0% schema coverage, the description does the work by explaining that passing an id targets one job while the whole queue is covered otherwise, giving the null default actual meaning. It does not specify the id format (string vs numeric) or what happens with an invalid id.

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 specific resource (render job / render queue) and a specific query verb, plus the fields returned. An agent can distinguish it from render_start or render_jobs by the 'status query only' framing, 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?

Usage is only implied: the parenthetical 'one render job or of the whole queue' combined with the optional job_id signals that omitting the id queries the entire queue. There is no explicit when-to-use or when-not-to-use guidance relative to status, render_jobs, or render_start.

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