Skip to main content
Glama

fusion_connect

Connects a Fusion tool's main output to another tool's input, letting you wire node graphs inside DaVinci Resolve; set disconnect to true to clear an existing input link.

Instructions

Wire from_tool's main output into to_tool.input (e.g. 'Input', 'Background', 'Foreground', 'EffectMask'). disconnect=true clears that input.

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": {
      "from_tool": "<from_tool>",
      "to_tool": "<to_tool>"
    },
    "name": "fusion_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNocurrent
compNo
inputNoInput
to_toolYes
from_toolYes
disconnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 usefully reveals that only the 'main output' is wired, that specific input socket names are targeted, and that disconnect=true removes the connection rather than adding one. It omits what happens if the target input is already occupied, whether a connection is created or replaced, and any failure/return behavior.

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?

Two tight sentences with the core operation front-loaded and the destructive variant stated immediately after. No filler, and the socket examples earn their space by clarifying a non-obvious parameter.

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 six-parameter mutation tool with no annotations and no output schema, the description covers the essential mechanics — endpoint nodes, target socket, and disconnect. The gaps (comp/clip scoping, replacement behavior on an occupied input, return value) are real but secondary to calling it correctly.

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 compensate for six parameters. It gives real semantics for from_tool, to_tool, input, and disconnect (4 of 6), but leaves clip and comp — the ones that determine which comp and clip the wiring happens in — completely unexplained.

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+resource: wiring one Fusion tool's main output into another tool's named input. The parenthetical input examples ('Input', 'Background', 'Foreground', 'EffectMask') make the operation concrete. It does not explicitly distinguish itself from siblings like fusion_set or fusion_tool_add, so it stops short of a 5.

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 versus alternatives, no prerequisites (do both tools need to exist in the comp already?), and no exclusions. The only usage-adjacent information is the disconnect=true variant, which is a parameter behavior rather than a selection rule.

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