Skip to main content
Glama
Sign In
video-sense

video-sense

by znplusW
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

video_frame

Read-only

Retrieve a larger single frame from a local video at a requested timestamp to inspect details missed in a storyboard.

Instructions

Retrieve a larger single frame at a requested source-video second for details missed in a storyboard. Input is an absolute local path; no audio. Does not guarantee exact original frame PTS. Images default to format=jpeg (FFmpeg q:v4, 4:4:4); request format=png for original PNG detail. Encoding is cancellable with 2 active conversions per MCP process, at most 24 queued, a 30s queue deadline and a 10s execution deadline. Every image response is limited to 8MiB encoded bytes. This is a stateless single-frame query without a review batch.

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": {
      "file": "<file>",
      "seconds": "<seconds>"
    },
    "name": "video_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYes
formatNo
qualityNo
secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: it takes an absolute local path, returns no audio, may not use the exact original frame PTS, defaults to JPEG with FFmpeg q:v4 4:4:4, supports PNG, is cancellable, has concurrency and queue limits, enforces deadlines, and caps encoded images at 8MiB. This is substantial operational context that annotations alone do not provide.

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 front-loaded with the core purpose and then efficiently layers operational constraints, format behavior, cancellation limits, and deadlines. Every sentence adds information useful for correct invocation, with no obvious filler.

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 stateless image-retrieval tool with annotations and no output schema, the description is mostly complete: it covers input path semantics, timing, format defaults, size limits, and execution constraints. The main remaining gap is the unexplained quality parameter.

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%, so the description must carry parameter meaning. It explains file as an absolute local path, seconds as the requested source-video second with a PTS caveat, and format defaulting to jpeg with png available, but it does not explain the quality parameter or its low/standard/high/ultra enum values.

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 states a specific verb and resource: retrieve a larger single frame at a requested source-video second. It distinguishes itself from the storyboard workflow by explaining that this is for details missed in a storyboard, and it clarifies that it is a single-frame query rather than a review batch.

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?

It gives clear usage context by saying the tool is for details missed in a storyboard and is a stateless single-frame query without a review batch. It does not explicitly name sibling tools or fully spell out when not to use it, but the context is sufficient to route an agent.

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