Skip to main content
Glama

frames_contact

Generates a labelled contact sheet of DaVinci Resolve timeline frames in one image, using explicit times or evenly spaced frames to review and verify an edit.

Instructions

Contact sheet of several timeline frames in ONE image (labelled with their times). Give explicit times, or count frames spread evenly between start/end (default whole timeline). Great for reviewing a whole edit.

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

Input Schema

NameRequiredDescriptionDefault
endNo
countNo
startNo
timesNo
widthNo
columnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 burden. It usefully discloses that output is a single labelled image and that the default range is the whole timeline, which is real behavioral context. It says nothing about rendering cost, image return format, or how width/columns affect the result.

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?

Two short sentences, front-loaded with the output shape before the parameter mechanics. No filler; the only shortfall is that the second sentence packs selection logic and the weak 'Great for reviewing' rationale together.

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?

The core selection semantics are covered, which is the hardest part of this tool. But with no annotations, no output schema, and 0% schema coverage, the two layout parameters and the form of the returned image remain unexplained, leaving gaps an agent must guess at.

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% across 6 parameters, so the description must compensate. It does explain the important interlock: `times` takes precedence, otherwise `count` frames are spread evenly between `start` and `end`, defaulting to the whole timeline. `width` and `columns` are left entirely undocumented.

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 concrete resource and output: a contact sheet of several timeline frames rendered into ONE labelled image. The emphasis on a single combined image, plus 'reviewing a whole edit', effectively distinguishes it from single-frame siblings like frame_preview or media_frames, though none are named explicitly.

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?

There is implied guidance ('Great for reviewing a whole edit') and a clear fork between two invocation modes (explicit `times` vs `count` spread over start/end). However, it never says when to pick this over frame_preview or media_frames, nor any exclusions or prerequisites.

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