Skip to main content
Glama
Sign In
DaVinci Resolve MCP Server

DaVinci Resolve MCP Server

by guycochran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

resolve_analyze_slate

Run Slate ID analysis on a selected clip or folder, then add color-coded markers to identify each slate. Requires AI Slate ID Extras.

Instructions

Run native Slate ID analysis on a clip or folder and add slate markers. Requires AI Slate ID Extras.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_analyze_slate"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_nameNo
folder_pathNo
marker_colorNoGreen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.2.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the operation is an analysis that writes slate markers and requires the AI Slate ID Extras package, but it does not describe failure behavior, how existing markers are affected, or what a successful run returns.

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?

The description is two sentences with no filler. The main action is front-loaded, and the Extras prerequisite is presented as a clear terminal caveat.

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 description covers the essential action, target, outcome, and prerequisite, which is adequate for a simple tool. But with no annotations and no output schema, it omits expected return values, marker placement specifics, and behavior when the Extras requirement is unmet, so it is not fully complete.

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?

The phrase 'on a clip or folder' maps to clip_name and folder_path and implies they are alternatives, which adds meaning beyond the bare schema. However, it does not clarify interaction/precedence between those parameters or define marker_color behavior beyond the schema's title and default, leaving 0% schema coverage only partially compensated.

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 ('Run ... analysis') and resource ('on a clip or folder'), and states the observable result ('add slate markers'). This distinguishes it from sibling analysis/marker tools and makes the tool's purpose immediately clear.

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 description implies usage by naming the target and outcome, and it gives a hard prerequisite ('Requires AI Slate ID Extras'). However, it does not explicitly explain when to prefer this over related sibling tools such as resolve_analyze_intellisearch or resolve_add_marker.

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