Skip to main content
Glama

grade_lut

Apply or remove a LUT on a DaVinci Resolve color node for clips, timelines, or group pre/post grades. Specify a LUT path to color grade, or use an empty string to clear it.

Instructions

Apply a LUT to a node (path relative to the LUT folder, e.g. 'Film Looks/Rec709 Kodak 2383 D65.cube', or an absolute path inside a LUT folder). Use lut='' to remove. Targets: clip refs, 'timeline', 'group::pre|post'.

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": {
      "clips": "<clips>",
      "lut": "<lut>"
    },
    "name": "grade_lut"
  }
}

Input Schema

NameRequiredDescriptionDefault
lutYes
nodeNo
clipsYes
layerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 disclosure burden. It usefully explains path resolution and that lut='' removes an existing LUT, but says nothing about whether applying a LUT overwrites a prior one, what happens on an invalid path, permission requirements, or reversibility of the change.

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?

The definition is compact and front-loaded, leading with the action and immediately following with the path-format detail that prevents the most likely invocation error. The trailing target list is terse but earned; little is wasted, though the sentences could be split more cleanly.

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 is the only source of behavioral information for a four-parameter mutation tool. It covers the LUT argument and target selection well but leaves node and layer undefined and gives no indication of what the call returns or how failures are reported.

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, and it does well for two of the four parameters: lut (path form and empty-string removal) and clips (clip refs, 'timeline', 'group:<name>:pre|post'). It says nothing about node (only implied by 'apply to a node', default 1) or layer, which remain entirely undocumented.

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?

The description names a specific verb and resource — apply a LUT — and scopes it to a node, which clearly separates it from the sibling lut_list and lut_export utilities. The example path format makes the operation concrete enough to distinguish from grade_look or grade_cdl.

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?

It states clear operational context: the LUT argument takes a relative or absolute path inside the LUT folder, and an empty string removes the LUT. It also enumerates valid targets (clip refs, 'timeline', 'group:<name>:pre|post'). It stops short of naming sibling alternatives such as grade_look or grade_cdl for related grading tasks.

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