Run Lua scripts directly in DaVinci Resolve's Fusion environment to automate compositing, scripting, and custom video production tasks.
Execute a Lua script in Resolve's Fusion environment.
| Name | Required | Description | Default |
|---|---|---|---|
| script | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description must carry the full burden of disclosing behavioral traits. It simply says 'Execute a Lua script' without any warning about potential side effects, project mutation, or arbitrary code execution risks. This is a significant omission for a code-execution tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence and contains no filler, but it is under-specified. While it is technically concise, it lacks necessary details such as parameter usage or behavioral cautions, making it only minimally adequate rather than well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is a generic Lua execution command with no output schema, no annotations, and a single undocumented parameter. The description does not explain what kind of scripts run, whether results are returned, or what safety considerations apply. This is highly incomplete given the tool's power and ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema contains one required parameter, 'script,' with no description (schema description coverage is 0%). The description does not mention this parameter or provide any meaning, format, or examples, leaving the agent without information about what to supply.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function with a specific verb and resource: 'Execute a Lua script in Resolve's Fusion environment.' This distinguishes it from sibling tools like create_fusion_node, which create a specific node rather than running arbitrary code.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The context 'in Resolve's Fusion environment' implies a scope, but there is no explicit when-to-use or when-not-to-use instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.