Skip to main content
Glama

generator_add

Adds standard, Fusion, or OFX generators—including empty compositions—to a DaVinci Resolve timeline at a chosen time, track, and duration for building or filling edits.

Instructions

Add a generator (kind: standard → 'Solid Color', '10 Step', 'Grey Scale', 'SMPTE Color Bar', 'Four Color Gradient', 'Window'; fusion → Fusion generators e.g. 'Contours', 'Noise Gradient'; ofx → OFX generator names; composition → empty Fusion composition to build with fusion_* tools) at time/track for duration seconds.

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": "generator_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo
kindNostandard
nameNoSolid Color
labelNo
trackNoV1
durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It states that the tool adds a generator at a time/track for a duration, but it does not disclose mutation side effects, permissions, overwrite behavior, return format, or what happens with label.

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?

The description front-loads the action and then uses a compact parenthetical to enumerate kind options. It is dense and somewhat list-heavy, but the structure is efficient and every part adds useful selection detail.

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 six-parameter mutation tool with no annotations and no output schema, the description covers the core placement and kind semantics well. It still omits label behavior, default values, and mutation/return details that would help an agent call it confidently.

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?

Schema description coverage is 0%, so the description must compensate. It meaningfully defines kind categories with examples and names, and explains at, track, and duration behavior in seconds; only label remains undocumented.

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 and resource: "Add a generator." It also enumerates generator kinds and clarifies the special composition case for building with fusion_* tools, making the purpose clear, though it does not directly contrast with sibling add tools such as title_add or transition_add.

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 kind mapping provides useful selection guidance: standard generators, Fusion generators, OFX generators, and empty Fusion compositions. However, it does not explicitly state when to use this tool versus alternatives like title_add or fusion_tool_add, so the usage guidance is implied rather than complete.

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