Skip to main content
Glama

fusion_comps

Manage Fusion compositions on a DaVinci Resolve timeline clip: list, add, load, rename, delete, import, or export .comp files to build and reuse node-based effects.

Instructions

Fusion compositions of a timeline clip. action: list | add | load (name) | delete (name) | rename (name→new_name) | import (.comp/.setting path) | export (comp index → path).

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

Input Schema

NameRequiredDescriptionDefault
clipYes
nameNo
pathNo
indexNo
actionNolist
new_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 burden. It usefully pairs parameters with actions and names accepted import file types (.comp/.setting), but it does not disclose side effects, whether delete/rename are irreversible, required permissions, or what list/add/export return.

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?

It is a single dense sentence with a pipe-delimited action list, front-loaded with the resource and free of filler. The fragment style is terse but not wasteful.

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 6-parameter, no-annotation, no-output-schema tool with seven actions, the description covers the invocation contract but omits behavioral context such as what list returns, what add does, and destructive warnings. It is minimum viable rather than complete.

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%, yet the description compensates well: it maps name to load/delete/rename, new_name to rename, path to import/export, and index to export. Only the required clip parameter and the action default are left to schema/context, so this is strong semantic coverage.

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?

The description names the resource ("Fusion compositions of a timeline clip") and enumerates seven operations, so an agent can infer that the tool manages comps. However, it opens with a noun fragment rather than a verb and never distinguishes this tool from siblings like fusion_comp_info or fusion_render_settings.

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 pipe-delimited action list hints at what each mode does, but there is no explicit when-to-use guidance versus alternatives, no prerequisites for load/import, and no exclusions. Action selection is left implicit.

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