Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by angelOnly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

apply_still

Apply a saved still grade to a named clip, or to the current clip when no name is provided.

Instructions

Apply a still (grade) to a clip by name, defaulting to current clip if none specified.

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": {
      "still_name": "<still_name>"
    },
    "name": "apply_still"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_nameNo
still_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose consequences. It does not state whether applying a still overwrites existing grades, is reversible, or what happens if the still/clip name is invalid, leaving the safety profile incomplete.

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?

Single sentence, front-loaded with the action and resource, no wasted words.

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?

The tool is small and the main invocation logic is covered, but as a mutation without annotations it lacks side-effect/failure details and any mention of prerequisites (e.g., a saved still must exist). Still, it is adequate for basic invocation.

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?

With 0% schema coverage, the description compensates by explaining both parameters: still_name is a name and clip_name is optional with a current-clip default. This adds meaningful semantics beyond the schema's field titles, though it doesn't describe value formats or constraints.

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 uses a specific verb ('Apply') and identifies the resource ('a still (grade) to a clip by name'), clearly distinguishing it from sibling save_still. It also immediately states the default behavior for unspecified clip.

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?

It indicates the primary context: applying a saved grade to a named clip, with fallback to the current clip. However, it does not explicitly contrast with save_still or other color tools, though the workflow is implicit.

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