Skip to main content
Glama

set_cdl

Apply an ASC CDL grade to a timeline item node by setting slope, offset, power, and optional saturation values for precise color correction.

Instructions

Set an ASC CDL on a node of a timeline item's grade (slope / offset / power as [r, g, b]).

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": {
      "item": "<item>",
      "slope": "<slope>",
      "offset": "<offset>",
      "power": "<power>"
    },
    "name": "set_cdl"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
nodeNo
powerYes
slopeYes
offsetYes
saturationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already disclose that this is a non-read-only, non-destructive mutation with no open-world behavior. The description adds useful context that the CDL is applied to a node of a timeline item's grade and explains the RGB component structure. However, it does not state whether existing CDL values are overwritten, what permissions are required, or what happens to the node's grade beyond the supplied values.

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

Conciseness5/5

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

The definition is a single tightly constructed sentence with no filler. The core operation and the RGB interpretation are front-loaded. It is appropriately sized for the information it chooses to convey.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter mutation tool with no schema parameter descriptions and no output schema, the description is too sparse. It omits saturation entirely and does not clarify item, node default, value ranges, or mutation side effects. It gives enough context to recognize the tool's general purpose but not enough to invoke it confidently without inspecting the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across six parameters, so the description must carry parameter semantics. It explains slope, offset, and power as [r, g, b] arrays and references a node, but it does not explain the item parameter, the node default, the saturation parameter, or expected value ranges. Three of the six parameters receive some semantic help, leaving notable gaps.

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 states a specific verb (Set), a specific resource (ASC CDL), and the target location (a node of a timeline item's grade). It clarifies that slope, offset, and power are RGB arrays. It does not explicitly distinguish this from sibling grade tools such as apply_grade or copy_grade, but the purpose itself is clear.

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?

The description explains what the tool does but gives no guidance on when to use it instead of related grade tools or what prerequisites must be met. There is no mention of when CDL setting is appropriate versus applying a grade or copying a grade. Usage is only implied by the operation described.

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