Skip to main content
Glama

lut_export

Export a clip's color grade as a LUT file in 17, 33, 65, or Panasonic sizes, giving AI assistants a portable grade reference for DaVinci Resolve workflows.

Instructions

Export a clip's grade as a LUT file. size: 17 | 33 | 65 | panasonic.

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>",
      "path": "<path>"
    },
    "name": "lut_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYes
pathYes
sizeNo33

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are present, so the description carries full behavioral burden. It discloses that the output is a LUT file and lists size options, but does not explain overwrite behavior, destination path requirements, LUT format, permissions, or what happens on failure.

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?

The description is two short sentences with the main action front-loaded and no wasted wording. The size enumeration is compact and directly relevant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a file-export tool with no annotations, no output schema, and 0% schema parameter descriptions, the definition is too thin. It omits key operational details such as path semantics, output file naming, overwrite policy, and LUT format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters. The description usefully enumerates size values (17, 33, 65, panasonic), which the schema does not, but it leaves clip and path essentially unexplained, including whether path refers to a file or directory and what extension is expected.

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 states a specific verb and resource: "Export a clip's grade as a LUT file." This is clear enough that an agent knows the operation, but it does not explicitly distinguish this tool from nearby siblings such as grade_lut or lut_list.

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 alternatives like grade_lut, lut_list, or the other export tools. The description only states the action, leaving all routing conditions to the agent's inference.

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