Skip to main content
Glama

grade_copy

Copies a clip's current node-stack grade to other clips, an entire V1 track, or selected clips to apply the same color grade across a timeline.

Instructions

Copy the grade (current node stack layer) from one clip to other clips (refs, 'V1' for a whole track, 'selected').

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": {
      "source": "<source>",
      "targets": "<targets>"
    },
    "name": "grade_copy"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
targetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does useful work by defining what is transferred (only the current node stack layer, not the entire stack) and by listing the target forms, but it never states whether the destination clips' existing grades are overwritten or merged, whether the operation is undoable, or what happens to clips that have no grade.

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 compact sentence with the action front-loaded and the target syntax parenthesized where it is needed. Nothing is redundant, though the parenthetical list is dense enough that it reads faster than it parses.

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 two-parameter tool with no annotations and no output schema, the description covers purpose and one parameter's value forms. It is adequate to attempt a call, but the meaning of 'source' and the overwrite/return behavior are left for the agent to guess.

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. It does partially: 'targets' is explained as accepting clip refs, 'V1' for an entire track, or 'selected', which is real syntax the schema does not provide. The 'source' parameter is left uncharacterized — presumably a single clip reference — and the accepted forms for it are undocumented.

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 gives a concrete verb plus resource ('Copy the grade ... from one clip to other clips') and clarifies that 'grade' means the current node stack layer, which separates it from the grade_lut/grade_cdl/grade_look siblings that apply or create grades rather than copying them. It stops short of naming a sibling explicitly, so it is clear rather than fully differentiated.

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 the verb: use it when an existing grade must be replicated onto other clips. There is no explicit when-not guidance, no mention of alternatives such as applying a LUT or resetting a grade, and no stated prerequisites such as needing a clip context or selection.

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