Skip to main content
Glama

Outil.io

Get video source frame

get_video_source_frame
Read-only

Voir une vraie image JPEG d’un rush à un temps source précis. Utiliser plusieurs temps pour comprendre une scène ; ne déduit pas le contenu audio.

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": {
      "assetId": "<assetId>"
    },
    "name": "get_video_source_frame"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNo
assetIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds value beyond them: it says the output is an actual JPEG image (not metadata or a summary) and that audio content is not inferred. That audio limitation is a meaningful capability boundary an agent would otherwise have to discover by trial.

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?

Two short sentences, no filler: the capability comes first, then the usage hint and the audio caveat. Slightly dense semicolon construction, but every clause carries information.

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 read-only, no-output-schema tool, the description covers the essential unknowns: that the return is a real image and that audio is out of scope. Missing only the time bounds and any note on image resolution or cost of repeated sampling.

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 carries the burden for two parameters. It does clarify that `time` is a source time (a real semantic distinction from timeline or export time), but it never explains `assetId` or the 0–3600 second range, leaving half the parameters undocumented in both places.

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?

"Voir une vraie image JPEG d'un rush à un temps source précis" names a concrete verb (voir) and resource (a real JPEG frame of source footage) and pins the temporal coordinate to source time. It does not explicitly distinguish itself from the sibling get_video_export_frame, so the source-vs-export distinction must be inferred from the word "rush".

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?

"Utiliser plusieurs temps pour comprendre une scène" gives real working guidance on how to sample the tool, and "ne déduit pas le contenu audio" sets a boundary on what it can answer. However, there is no explicit statement of when to prefer this over get_video_export_frame or other inspection siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.