Skip to main content
Glama

color_versions

Manage color versions of a DaVinci Resolve clip by listing, adding, loading, deleting, or renaming versions, including remote versions.

Instructions

Color versions of a clip. action: list | add | load | delete | rename. remote=true uses remote versions.

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": {
      "clip": "<clip>"
    },
    "name": "color_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
nameNo
actionNolist
remoteNo
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it never states that delete/rename are destructive or irreversible, what permissions are required, or what happens to the clip's active version. The only real behavioral disclosure is the remote=true flag semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with no padding, and the resource is stated first, but the telegraphic fragments ('action: list | add | load | delete | rename.') read like notes rather than guidance, and brevity here costs more than it saves.

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?

Considered as a 5-parameter, 5-operation mutation tool with no annotations and no output schema, the definition is too thin: it omits per-action parameter requirements and any notion of return values or failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and all five parameters are bare. The description rescues action (five valid values) and remote, but clip, name, and new_name are unexplained, and crucially it does not map which parameters apply to which action (e.g. new_name only for rename).

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

Purpose3/5

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

'Color versions of a clip' names the resource and the action list (list/add/load/delete/rename) tells an agent this is a version-management tool, but the opening is a noun phrase rather than a verb+resource statement and there is no differentiation from siblings such as color_groups or clip_properties.

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?

The action list hints at possible operations, but nothing says when to use add versus load, which actions mutate state, or how this differs from color_groups. An agent must infer the workflow entirely.

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