Skip to main content
Glama

list_gallery

Read-only

Lists Still and PowerGrade albums in DaVinci Resolve, including the current album and optional still indexes and labels.

Instructions

Still and PowerGrade albums (refs 'album:still:' / 'album:powergrade:'), the current album, and optionally each album's stills (index and label).

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

Input Schema

NameRequiredDescriptionDefault
with_stillsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered and the description's remaining burden is low. It does add value by disclosing the shape of the result (albums, the current album, and per-album stills with index and label), which substitutes for the absent output schema, but says nothing about ordering, empty galleries, or pagination.

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?

A single compact sentence with no filler, and the principal resource (albums plus their refs) is front-loaded ahead of the optional stills expansion. It reads as a noun-phrase fragment rather than a complete statement, which is a minor structural weakness but costs no tokens.

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 one-optional-boolean read tool with no output schema, the description covers the returnable content and the effect of the flag, which is most of what an agent needs. It stops short of guidance on when to choose this over other list_* tools or whether these album refs are reusable as inputs elsewhere, leaving a real gap for a gallery-discovery call.

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 coverage is 0% for the single with_stills boolean, so the description carries the full explanatory load. It partially does: the phrase 'and optionally each album's stills (index and label)' tells the agent exactly what toggling the flag adds to the response, though it never names the parameter or states the default of false.

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 enumerates the resource precisely: Still and PowerGrade albums with their exact reference syntax ('album:still:<n>' / 'album:powergrade:<n>'), the current album, and optionally each album's stills. It lacks an explicit verb and never names a sibling to differentiate from, but the resource scope is unambiguous enough that an agent knows what is being enumerated.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool (e.g. list_presets or list_color_groups) for enumerating other gallery-adjacent resources. The only hint of usage is the word 'optionally', which signals the with_stills choice but not when to make 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