Skip to main content
Glama

presets

Manage DaVinci Resolve application configurations: list, load, save, update, delete, import, or export layouts, keyboard mappings, render settings, and Fairlight timeline setups by kind.

Instructions

Manage application presets. kind: layout | keyboard | burn_in | project_settings | render | user_prefs | fairlight. action: list | load | save | update | delete | import | export (not every kind supports every action). 'fairlight' + 'load' applies a Fairlight preset to the current timeline.

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": {
      "kind": "<kind>"
    },
    "name": "presets"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameNo
pathNo
actionNolist

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 supplied, the description carries the full behavioral burden. It usefully discloses the action space, the constraint that kind/action combinations vary, and the special 'fairlight' + 'load' timeline behavior, but it does not cover permissions, reversibility, overwrite behavior, or what destructive actions affect.

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?

The description is dense, front-loaded, and free of obvious filler. The kind and action lists are compressed but readable; the special case is appended clearly.

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 four-parameter preset-management tool with no annotations and no output schema, the description leaves important gaps: name and path semantics, action-specific effects, safety for delete/import/export, and return behavior. It explains the option space but not enough to call the tool confidently in all cases.

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

Parameters3/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 supply parameter meaning. It adds valuable enum-like semantics for 'kind' and 'action', including the fairlight/load relationship, but it says nothing about the 'name' and 'path' parameters.

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 and resource ('Manage application presets') and enumerates supported kinds and actions, so the tool's scope is clear. It does not explicitly distinguish itself from nearby siblings such as project_settings or save, so it falls short of full sibling differentiation.

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?

The action list and the note that 'not every kind supports every action' imply how to use the tool and help avoid invalid combinations. However, there is no explicit when-to-use guidance or routing versus alternatives like project_settings or save.

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