Skip to main content
Glama

apply_grade

Applies .drx grade files with no keyframes, source timecode alignment, or start-frame alignment; also applies ARRI CDL+LUT metadata or resets graph grades.

Instructions

Apply a .drx grade file (grade_mode 0 = no keyframes, 1 = source timecode aligned, 2 = start frames aligned), apply the ARRI CDL+LUT from clip metadata, or reset all grades of a graph.

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

Input Schema

NameRequiredDescriptionDefault
layerNo
resetNo
targetYes
drx_pathNo
grade_modeNo
arri_cdl_lutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the mutation/safety profile is covered. The description adds real value by explaining what the three operations do and what the grade_mode values mean, but it does not clarify whether grading targets a clip, a layer, or a whole graph, nor which combination of flags takes precedence.

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?

A single dense sentence that front-loads the primary action and uses a parenthetical for enum decoding, with no filler. It is readable, though 'graph' is undefined jargon and the nested comma-separated clauses make it slightly harder to parse than necessary.

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?

The description explains the three operating modes and the enum values, which covers the core behavioral surface of this tool. However, with no annotations detail and no explanation of target, layer, or flag precedence, an agent still has to guess the scope of the operation before invoking it.

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 carries the full burden. It decodes the grade_mode enum and maps the .drx, ARRI CDL+LUT, and reset operations to their likely flags, but the only required parameter (target) and layer are never explained, leaving significant ambiguity for a 6-parameter tool.

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 specific verbs and resources: apply a .drx grade file, apply the ARRI CDL+LUT from clip metadata, or reset all grades of a graph. An agent can tell it is a grade-mutation tool distinct from preset-oriented siblings like apply_fairlight_preset or copy_grade, though it never says so explicitly.

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?

The three-way 'or' structure implies mutually exclusive modes, and grade_mode values are decoded, which hints at when to use each mode. But there is no explicit guidance on choosing between these modes and siblings such as copy_grade or apply_fairlight_preset, and no statement of what happens if reset=true is combined with drx_path or arri_cdl_lut.

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