Skip to main content
Glama

set_node

Configure a DaVinci Resolve node by assigning or clearing a LUT, toggling it on or off, or setting its cache mode; refresh LUTs after adding files.

Instructions

On one node (1-based) of a graph: set a LUT (absolute path or relative to the LUT folders; "" clears; run refresh_luts after adding LUT files), enable/disable it, or set its cache mode.

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": {
      "target": "<target>",
      "node": "<node>"
    },
    "name": "set_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
lutNo
nodeYes
cacheNo
layerNo
targetYes
enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. Beyond that the description discloses the 'clearing' behavior of an empty LUT string and the refresh_luts dependency, but says nothing about persistence, undo, or whether target refers to a project/graph scope. Useful but not rich.

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?

One dense, front-loaded sentence that puts the scope ('on one node of a graph') first and keeps parentheticals tight. It is efficient, though the parentheticals stack enough detail that a short second sentence separating the three modes would read 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?

For a mutation tool with no output schema and 0% schema description coverage, the description covers the core behaviors but leaves target and layer unexplained and gives no hint of the return value or error conditions. An agent could call it for the LUT/enable/cache cases but would be guessing on the remaining parameters.

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% for six parameters, so the description must compensate. It does explain lut (path resolution and the empty-string clear), enabled, and cache semantics, plus the 1-based indexing of node. However, layer and target, two of the six parameters, are never mentioned, leaving real gaps.

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 ('On one node ... set a LUT ... enable/disable it, or set its cache mode') and scopes it to a single node of a graph, which distinguishes it from siblings such as get_node_graph and reset_node_colors. It also disambiguates itself from refresh_luts by naming that tool as a follow-up step rather than an alternative.

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 gives concrete operational guidance: LUT paths may be absolute or relative to the LUT folders, an empty string clears the LUT, and refresh_luts must be run after adding LUT files. It does not state when to use this versus other node-editing siblings (e.g. color resets or CDL setters), but the three modes of use are clear.

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