Skip to main content
Glama

export_cube_lut

Export a single Color DNA or blended multi-DNA mix as a 33x33x33 .cube 3D LUT for use in DaVinci Resolve, Premiere Pro, Final Cut Pro, and CapCut.

Instructions

Export a single Color DNA or a blended multi-DNA mix as a standard 33x33x33 .cube 3D LUT compatible with DaVinci Resolve, Adobe Premiere Pro, Final Cut Pro, and CapCut.

Args: output_cube_path: Destination .cube file path. dna_id: Single Color DNA ID (provide either dna_id or weights). weights: Optional blend weights dict e.g. {"film_emulation_001": 0.7, "cinematic_teal_orange_002": 0.3}. title: Title embedded inside the .cube file header. size: 3D LUT cube resolution (default: 33, standard for video NLEs). slider_overrides: Optional slider adjustments applied before baking the LUT. catalog_path: Optional custom path to color_dna_catalog.json.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "output_cube_path": "<output_cube_path>"
    },
    "name": "export_cube_lut"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
titleNoChromaDNA LUT
dna_idNo
weightsNo
catalog_pathNo
output_cube_pathYes
slider_overridesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses output format compatibility, that slider_overrides are applied before baking, and the standard default size, but says nothing about whether an existing file at output_cube_path is overwritten, computational cost of baking at higher sizes, or failure modes for an unknown dna_id.

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?

Front-loaded with the one-line purpose, then a scannable Args list with one line per parameter and no filler. The raw docstring 'Args:' framing is slightly mechanical but does not waste words.

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?

With seven parameters, zero schema descriptions, and no annotations, the description supplies the missing parameter meaning and the output format contract, and an output schema exists so return values need not be restated. What remains thin is operational behavior (overwrite semantics, catalog_path usage) for a file-writing tool.

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?

Schema description coverage is 0%, so the Args block does the entire job and mostly succeeds: it defines the either/or relationship between dna_id and weights, gives a concrete weights example dict, and explains title as header metadata and size as NLE-standard resolution. It stops short of explaining catalog_path's role or slider_overrides' key vocabulary, so it is strong but not exhaustive for seven parameters.

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 (Export), a specific resource (a single Color DNA or blended multi-DNA mix), and the exact output artifact (33x33x33 .cube 3D LUT) plus the NLEs it targets. The format and resolution specificity makes it unmistakable relative to siblings like render_preview or blend_color_dna.

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 implied by the output artifact: it embeds a LUT file, so it is the terminal step of a color pipeline. However, it never states when to pick this over render_preview or compile_xmp_preset, nor does it name the prerequisite that the DNA or weights must exist (e.g. obtained via list_color_dna/inspect_color_dna).

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