Skip to main content
Glama

analyze_rendered_frames

Decode rendered video frames, detect black or frozen segments, and export sampled thumbnails for human review before editing.

Instructions

Decode the video; run black/freeze detection and export sampled thumbnails for human review.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>",
      "outputDirectory": "<outputDirectory>"
    },
    "name": "analyze_rendered_frames"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputDirectoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the non-destructive-but-writing profile is already conveyed. The description adds that it decodes the video, writes sampled thumbnails to disk and relies on human review, but does not disclose how many thumbnails, detection thresholds, or runtime cost.

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 compact sentence with the core actions front-loaded and no filler. The semicolon-separated clause structure keeps the three steps readable.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. However, with both parameters undocumented and no explanation of detection thresholds or output artifacts, an agent still lacks key invocation details.

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

Parameters2/5

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

Schema coverage is 0%: neither 'input' nor 'outputDirectory' is described in the schema. The description implies input is the video and that thumbnails are written to the output directory, but it never states format, path expectations, or whether the directory must exist.

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 specific verbs and resources: decode the video, run black/freeze detection, export sampled thumbnails. It is clearly a render-inspection tool, though it does not name how it differs from siblings like inspect_render or generate_quality_report.

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?

The phrase 'for human review' hints at the situation, but there is no explicit when-to-use guidance, no prerequisites (what video source it needs), and no mention of alternatives such as inspect_render for programmatic checks.

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