Skip to main content
Glama

copy_grade

Copies the current grade from one timeline item to multiple target items in DaVinci Resolve, enabling consistent color adjustments across clips.

Instructions

Copy the current grade of one timeline item onto other items.

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": "copy_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
targetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false but the description never states what happens to the targets' existing grades — overwrite, merge, or skip — which is the key behavioral question for a copy-onto-many operation. It also omits whether the copy is reversible and what happens when a target is missing or ungraded, so the description adds little beyond the annotation flags.

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 well-formed sentence with the resource and direction front-loaded and no filler. Nothing is wasted, though the extreme brevity is closer to under-specification than to disciplined concision.

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 mutation tool with no output schema, 0% parameter documentation, and only terse annotation flags, the definition does not cover overwrite semantics, identifier format, partial-failure behavior across multiple targets, or the result format. An agent could invoke it, but not confidently predict the effect on existing grades.

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 bare "Source" and "Targets" titles carry no semantics, but the description does clarify the roles: source is the single timeline item holding the current grade, targets are the other items receiving it. It still does not say what identifier format is expected (item ID? index?) or whether all targets must belong to the same timeline, which is the gap the low schema coverage leaves exposed.

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 names a specific verb ("Copy") and resource ("the current grade") plus the direction of transfer (one timeline item onto other items), so an agent knows exactly what happens. It does not, however, distinguish this from the sibling apply_grade, leaving the copy-vs-apply distinction to inference.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., that the source must already have a grade), and no reference to an alternative such as apply_grade. The only usage signal is the implicit "you have one graded item and want others to match it."

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