Skip to main content
Glama

render_options

Lists available render formats, codecs, resolutions, render presets, quick-export presets, and current format, codec, and render mode to help you choose valid DaVinci Resolve output settings.

Instructions

What can be rendered: formats (name → extension), codecs for format (extension like 'mp4', 'mov'), resolutions for format+codec, render presets, quick-export presets, current format/codec and render mode.

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

Input Schema

NameRequiredDescriptionDefault
codecNo
formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. It never states that the call is side-effect free, what the return structure looks like, or how the optional format/codec inputs change the result — it only names categories of data.

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?

A single front-loaded sentence that lists return categories without filler. It reads slightly as a run-on catalog, but nothing is wasted.

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 and no annotations, the description must cover both return values and behavior. It does a reasonable job listing what comes back, but leaves the two input parameters and the read-only nature unexplained, which is a meaningful gap for a discovery 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 coverage is 0%, so the description must compensate for the two undocumented parameters. It partially does: 'codecs for `format`' and 'resolutions for format+codec' imply a dependency/filtering relationship, but it never explicitly says passing format narrows codecs or that both are optional, leaving the actual call semantics inferential.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates what the tool returns (formats, codecs, resolutions, presets, current format/codec and render mode), which is specific content, but the verb is implicit — 'What can be rendered' does not say it is a read-only capability lookup rather than an action. An agent could plausibly misread it as performing a render given siblings like render_start and render_timeline.

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 when-to-use guidance, no mention of querying before calling render_start or render_timeline, and no statement of whether the two parameters are filters or optional selectors. The agent must infer the workflow entirely from the parameter names.

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