Skip to main content
Glama
furculaindignity7033

yueying

by furculaindignity7033
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_frames

Read-onlyIdempotent

Get 3x3 keyframe contact sheets or single frames from a video to see what's on screen, read code, slides, or UI text. Start with sheets, then request labelled frames as needed.

Instructions

See what is on screen in an already-watched video. Returns contact-sheet images (3x3 keyframes in time order, every tile labelled '#number mm:ss' bottom-left) or individual keyframes. Read the contact sheets first to get the visual storyline, then request single frames only when you need to read code, slides or UI text. At most 3 images per call (default 2), downscaled to max_width; page with start/count. Every image is preceded by its absolute file path so hosts that can read files may open the full-size original instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNogrids = 3x3 contact sheets, 9 keyframes per image (start here); frames = individual full-size keyframesgrids
countNoImages per call; keep 2 or fewer in Claude Desktop
startNo1-based number of the first image: contact-sheet number for grids, keyframe number (as printed on the tiles) for frames
videoYesvideo_id, results folder, or the path/URL given to watch_video
max_widthNoDownscale width in pixels; 1280 is about 150 KB per contact sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds substantial behavioral detail: tile labels with '#number mm:ss', the 3-image cap, downscaling to max_width, paging via start/count, and the absolute-file-path prefix. This goes well beyond the structured annotations.

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?

The description is dense but well organized: purpose first, then usage strategy, then limits and paging, then file-path behavior. Every sentence contributes actionable information, and there is no filler.

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

Completeness5/5

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

There is no output schema, so the description must carry the burden of explaining return values; it does so thoroughly, including image layout, labels, ordering, size limits, and host file access. The tool is simple enough that nothing needed for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real value by explaining the paging relationship between start/count, the meaning of kind ('grids' vs 'frames'), and the practical effect of max_width. This helps an agent use the parameters more correctly than the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Returns contact-sheet images... or individual keyframes') and the resource ('an already-watched video'), and it distinguishes the two output kinds, grids vs. frames. This makes the tool's purpose concrete and separates it from related frame-retrieval tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to 'Read the contact sheets first... then request single frames only when you need to read code, slides or UI text,' which is strong when-to-use guidance within the tool. It also gives paging and count guidance, though it does not explicitly name sibling alternatives like get_frame_at for single-frame needs.

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