Skip to main content
Glama

stills

Manage DaVinci Resolve gallery snapshots: list albums, grab frames, export/import files, delete entries, and apply snapshot grades to clips via DRX.

Instructions

Gallery stills. action: list (albums + still labels) | grab (still of the current clip at the playhead; Color page) | grab_all (one still per clip; frame_source first|middle) | export (stills indices of album to folder; format png|jpg|tif|dpx|cin|tga|bmp|exr|drx) | import (files) | delete (indices) | apply (grade of still indices[0] → clips, via DRX) | new_album | set_album (album name or index). powergrade=true works with PowerGrade albums.

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": "stills"
  }
}

Input Schema

NameRequiredDescriptionDefault
albumNo
clipsNo
filesNo
actionNolist
folderNo
formatNopng
prefixNostill
indicesNo
powergradeNo
frame_sourceNomiddle

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It hints at behavior for apply (grade of still indices[0] becomes clips via DRX) and grab (current clip at playhead), but says nothing about delete permanence, export overwrite behavior, permissions, or whether import mutates albums. For a tool containing destructive operations, this is a substantial gap.

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 action list is front-loaded and dense with no filler. The semicolon-heavy formatting is compact but makes the action-to-parameter mapping slightly harder to scan.

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 10-parameter tool with no annotations and no output schema, the description covers most actions and parameters but leaves safety, defaults, error conditions, and output details unstated. It is adequate to attempt a call but not complete enough for correct handling of destructive or export operations.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: album, clips, files, indices, folder, format, frame_source, and powergrade are all given meaning. It omits prefix entirely and does not specify what clips accepts or default behaviors, which keeps it below a 5.

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 the resource (gallery stills) and enumerates concrete actions: list, grab, grab_all, export, import, delete, apply, new_album, set_album. Each action is tied to a specific effect, so an agent can tell it is a stills-management tool. It does not differentiate itself from siblings such as frame_preview or frames_contact, which is the only thing keeping it from a 5.

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 parenthetical notes imply when each action applies (e.g. grab is 'Color page', export takes album/indices/folder), but there is no explicit guidance on choosing between actions or versus sibling tools. An agent can infer intent but must reason about preconditions like being on the Color page.

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