Skip to main content
Glama

lut_list

Lists LUT files known to DaVinci Resolve and returns relative paths usable with grade_lut. Filter results by substring using the optional search parameter.

Instructions

List LUT files Resolve knows (relative paths usable in grade_lut). search filters by substring.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lut_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that it lists LUT files known to Resolve and that results are relative paths usable in grade_lut, but it omits pagination behavior, sort order, search matching details, and whether the default limit truncates results.

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 compact sentences with no wasted wording. The core purpose is front-loaded, and the `search` parameter behavior is appended efficiently.

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 simple two-parameter list tool, the description covers the main purpose and the filtering parameter. It is still incomplete because it does not explain the limit/pagination behavior or what the returned list looks like, and there is no output schema to fill that gap.

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 compensate. It meaningfully explains `search` as a substring filter, but completely omits `limit`, including its default of 200 and whether it caps the number of returned LUT files.

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 and resource: "List LUT files Resolve knows." It also explains the files are relative paths usable in grade_lut, which gives useful context and distinguishes it from a grading tool, though it does not explicitly differentiate from siblings such as lut_export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage by saying the listed paths are usable in grade_lut and that `search` filters by substring. However, it does not explicitly say when to use this tool versus alternatives, nor does it discuss when not to use it.

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