Skip to main content
Glama

get_render_options

Read-only

Retrieve available render formats, codecs, resolutions, current render settings, and presets for DaVinci Resolve, including audio-only options.

Instructions

Render formats (name -> extension), the codecs of format (an extension like 'mov'), the resolutions available for a format/codec, the current format/codec and render mode (0 = individual clips, 1 = single clip) and render presets. audio=true lists audio-only formats/codecs.

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": "get_render_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioNo
codecNo
formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing that the result set is conditional on the supplied arguments (codecs require a format, resolutions require format/codec) and by decoding render mode 0/1, which is real behavioral context an agent could not get from the annotations.

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

Conciseness3/5

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

It is short, but it is a single run-on sentence built from stacked parentheticals, so the reader has to parse a list rather than a front-loaded statement of purpose. The audio hint is tacked on at the end instead of being grouped with the parameter explanation.

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?

With no output schema, the description must convey return content, and it does so at a category level. However, it never states what happens with zero arguments (does it return all formats, or only current settings?), which is a meaningful gap for a tool whose entire contract is a variable-shaped read.

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 carries the burden. It does clarify 'format' with example syntax ('an extension like mov') and explains that audio=true yields audio-only entries, but 'codec' is only mentioned obliquely and there is no statement of default or no-argument behavior, leaving one of three parameters under-specified.

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 enumerates the exact resources returned: format->extension mapping, codecs of a format, resolutions for a format/codec, current format/codec plus render mode, and presets. That is specific enough to separate it from siblings like list_render_jobs or render_status, though it omits an explicit verb ('get') and leads with a noun list rather than 'Returns...'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus set_render_settings, start_render, or list_render_jobs; the only usage hint is that audio=true lists audio-only variants. An agent must infer that this is the discovery step before configuring a render.

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