Skip to main content
Glama

grade_cdl

Apply ASC CDL color corrections (slope, offset, power, saturation) to a timeline clip node for cumulative primary grading.

Instructions

Apply an ASC CDL to a node of timeline clips (cumulative primary: slope≈gain, offset≈lift/offset, power≈gamma inverse). Values: number (all channels) or [r,g,b]. Defaults: slope 1, offset 0, power 1, sat 1.

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>"
    },
    "name": "grade_cdl"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNo
clipsYes
powerNo
slopeNo
offsetNo
saturationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the operation is cumulative over the existing primary grade and gives defaults, but says nothing about permissions, undo/reversibility, behavior with invalid node indices, or what the call returns.

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?

Two dense sentences with the core operation front-loaded and the semantics in a compact parenthetical. No wasted framing, though the gain/lift/gamma aside takes a moment to parse.

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 6-parameter mutation tool with no annotations, no output schema, and zero schema coverage, the description covers value formats and defaults but leaves the node selector, clip reference format, and failure/return behavior undocumented. Adequate but with evident gaps.

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 coverage is 0%, so the description must compensate, and it largely does: it maps slope/offset/power to gain/lift/gamma, defines the value format as a scalar or [r,g,b], and gives defaults for slope, offset, power, and saturation. The 'node' parameter and the 'clips' argument format remain unexplained.

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?

States a specific verb and resource: 'Apply an ASC CDL to a node of timeline clips', which clearly separates it from LUT, DRX, and copy grading siblings. It does not explicitly name those alternatives, but the operation described is unambiguous.

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 'Apply an ASC CDL' and the note that it is a cumulative primary operation, which tells the agent it stacks on existing correction. There is no explicit when-to-use versus when-to-use-a-LUT/look guidance and no prerequisites such as node existence.

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