Skip to main content
Glama

export_lut

Export a timeline item's grade as a .cube LUT (17/33/65 points) or Panasonic VLUT to reuse color grades in other projects.

Instructions

Export a timeline item's grade as a LUT (.cube 17/33/65 points, or Panasonic VLUT).

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": {
      "item": "<item>",
      "path": "<path>"
    },
    "name": "export_lut"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
pathYes
sizeNo33

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already establish that this is a non-readonly, non-destructive, non-open-world operation, so the description need not restate safety. Beyond that, the description does not address what happens to an existing file at the path, whether the item must already have a grade, or what is returned; the format list mostly restates the size enum.

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 front-loaded sentence with no filler, and the format detail is grouped compactly in parentheses. It is efficient, but that efficiency comes at the cost of the missing semantics noted above.

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-writing mutation with three parameters and no output schema, the description is thin: it says nothing about overwrite behavior, path requirements, or failure conditions when the item has no grade. An agent could call it, but could not predict the result reliably.

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%, so the description must carry parameter meaning, but it never explains what 'item' identifies (a timeline item ID? name?) or what form 'path' takes (absolute filesystem path, relative to project?). It only implies that size maps to the enumerated LUT formats.

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 plus resource: it exports a timeline item's grade as a LUT, and it enumerates the output formats (.cube at 17/33/65 points or Panasonic VLUT). That clearly separates it from generic export siblings such as export_bin or export_timeline, though it does not explicitly name an alternative.

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 about when to choose this tool rather than the related copy_grade or apply_grade, and no prerequisites are stated. The agent is left to infer that this tool reads a grade into a file rather than applying or copying it.

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

Deploy Server

Other Tools