Skip to main content
Glama

get_current_frame_thumbnail

Read-only

Retrieve a PNG thumbnail of the current frame in DaVinci Resolve, using the Color page thumbnail when available and otherwise exporting the frame as a still so agents can view it.

Instructions

Image (PNG) of the current frame so the agent can see it: the Color page thumbnail when available, otherwise the frame exported as a still.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/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. The description adds real value beyond that by disclosing the return format (PNG) and the non-deterministic source selection: a Color page thumbnail when available, otherwise an exported still, which tells the agent the image may vary in nature.

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?

A single sentence with the output format and the source-selection rule front-loaded, and no wasted wording. Every clause carries information the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read tool with no output schema, the description covers what is returned (PNG), and how the image is chosen, which is the key unpredictability. It is silent on resolution, page/context dependencies, and what happens if no frame is available, which keeps it short of complete.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing parameter-level the description could add or omit. Held at the schema-driven baseline rather than maxed, since the description says nothing about the absence of filtering or scope options.

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: returns a PNG image of the current frame, and clarifies it is the Color page thumbnail or a still export of the frame. That distinguishes it in substance from export_current_frame, though it never names the sibling explicitly, so the agent must infer the routing.

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 phrase "so the agent can see it" implies the intended use (visual inspection), and the fallback rule is stated. However, there is no explicit guidance on when to prefer this over export_current_frame or other inspection tools, and no exclusions.

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