Skip to main content
Glama

create_stereo_clip

Combine left-eye and right-eye clips into a stereo 3D clip for DaVinci Resolve projects and timelines.

Instructions

Create a stereo 3D clip from a left-eye and a right-eye clip.

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": {
      "left": "<left>",
      "right": "<right>"
    },
    "name": "create_stereo_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
leftYes
rightYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing further: it doesn't say whether the source clips are modified or relinked, whether the new clip is added to a bin/timeline, or what the resulting object looks like.

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?

A single front-loaded sentence with no filler. Both the action and the source inputs are stated immediately, and nothing is repeated from the name.

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?

For a two-parameter creation tool with no output schema, the definition covers the core action but omits identifier format for the inputs and any indication of what is returned (e.g., new clip ID). Adequate but with clear gaps for an agent that must call this blind.

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 0%, so the description must carry the load. It does clarify that `left` and `right` are references to existing eye clips rather than arbitrary strings, which is meaningful beyond the schema's bare titles. However, it never states the expected identifier format (clip ID vs. name vs. path), so an agent still has to guess.

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?

The description gives a specific verb+resource ("Create a stereo 3D clip") and states the required inputs (left-eye and right-eye clip). It is clear enough to distinguish it from generic clip creation, though it does not explicitly name how it differs from siblings like create_compound_clip or create_multicam_clip.

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 guidance on when to use this tool versus the other create_* clip variants, nor any prerequisites (e.g., that both eye clips must already exist and be compatible). The agent must infer the selection condition from the name alone.

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