Skip to main content
Glama

clip_fade

Set fade-in and fade-out handles on video or audio clips in DaVinci Resolve using seconds; set 0 to remove a fade.

Instructions

Set video/audio fade-in/out handles on clips (seconds; 0 removes).

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": {
      "clips": "<clips>"
    },
    "name": "clip_fade"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipsYes
fade_inNo
fade_outNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does usefully reveal one non-obvious behavior — passing 0 removes the fade, and values are in seconds — but says nothing about what happens if the fade exceeds clip length, whether the edit is reversible, or what the response contains.

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, front-loaded sentence with no filler; the parenthetical is compact and load-bearing. Slightly denser jargon ('handles') could cost a novice a read, but nothing is wasted.

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

Completeness4/5

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

For a three-parameter mutation tool with no annotations and no output schema, the definition covers the core action and the key value semantics. Missing pieces (clip reference format, edge-case behavior for out-of-range fades) are real but secondary to calling the tool correctly on nominal inputs.

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 description must compensate; it does partially, clarifying units (seconds) and the sentinel value (0) for fade_in/fade_out. However, the required 'clips' parameter is completely uncharacterized — no indication whether it takes IDs, objects, or a list — which is the most consequential gap at 0% schema coverage.

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?

States a specific verb (Set) and resource (fade-in/out handles on clips), which clearly distinguishes it from sibling mutations like clip_speed or clip_trim. A reader knows exactly what changes on the clip, though the 'handles' terminology assumes domain familiarity.

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 and no alternative named; the agent gets no help deciding between this and, say, audio_normalize or clip_speed. The '(seconds; 0 removes)' parenthetical is a usage hint about values, not about when to invoke the tool.

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