Skip to main content
Glama

filmcraft_capture_frame

Captures the current rendered FilmCraft Program Monitor frame and saves it as a local image so AI vision models can visually inspect the timeline output.

Instructions

Captures the current rendered frame from the FilmCraft Program Monitor for AI vision models to inspect visually.

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

Input Schema

NameRequiredDescriptionDefault
outputFileNameNoLocal image file name to save the frame toprogram_frame.png

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It does disclose a meaningful behavioral fact beyond the name: the frame comes from the live Program Monitor (i.e. it snapshots whatever is currently rendered). It omits whether the tool mutates the project (implied non-destructive), that it writes a file to local disk (only in the schema), and whether the Program Monitor must be active.

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?

One front-loaded sentence with the verb and source first, no repetition. 'inspect visually' is slightly redundant with 'vision models' but still conveys intent efficiently.

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-parameter, no-output-schema tool this is close, but an agent still lacks the prerequisites (must a sequence be loaded / Program Monitor visible?) and the return contract (does it return the image, a file path, or only write to disk). With no annotations to fall back on, these gaps matter.

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 100% for the single optional parameter outputFileName, which already documents 'Local image file name to save the frame to'. The description adds no filename semantics, format constraints, or overwrite behavior, so the baseline 3 applies.

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 ('Captures') and a precisely-scoped resource ('the current rendered frame from the FilmCraft Program Monitor'), which is clearly different from siblings like filmcraft_export_sequence or filmcraft_inspect_timeline. It stops short of explicitly distinguishing itself from those neighbours, but the resource is concrete enough for an agent to disambiguate.

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 'for AI vision models to inspect visually' implies the use case (grab a visual snapshot to look at), but there is no explicit when-to-use/when-not, no prerequisite stated (an open project/sequence or active Program Monitor), and no alternative tool named for other visual-inspection needs.

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