Skip to main content
Glama
luquimbo

DaVinci Resolve MCP Server

by luquimbo

color_reset_grade

Destructive

Reset a clip's color grade to neutral CDL values (slope 1, offset 0, power 1, saturation 1) without deleting nodes.

Instructions

Reset a timeline item's grade to identity (neutral) CDL values.

Sets Slope=[1,1,1], Offset=[0,0,0], Power=[1,1,1], Saturation=1.0. This effectively neutralises the grade without removing nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_nameYesExact name of the timeline clip.
track_typeNoTrack type (default "video").video
track_indexNo1-based track number (default 1).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the destructiveHint annotation, the description adds the exact neutral CDL values (Slope, Offset, Power, Saturation) and clarifies that nodes are not removed. This gives the agent crucial behavioral insight about what the operation actually changes.

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?

Three short sentences, front-loaded with the primary action, then relevant details. No filler. Every sentence earns its place.

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

Completeness5/5

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

The tool is simple with only three parameters and an output schema. The description fully explains the effect, the target, and the key nuance (nodes preserved). Nothing essential is missing.

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 coverage is 100%, so the input schema already documents all parameters. The description mentions 'timeline item' which maps to item_name, but adds little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool resets a timeline item's grade to identity CDL values, which is a specific verb+resource combination. It distinguishes itself from siblings like color_set_cdl by focusing on the reset-to-neutral behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it: to neutralize a grade without removing nodes. It provides clear context for the operation but does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/luquimbo/davinci-resolve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server