Skip to main content
Glama
Sign In
Foldline

Foldline

by alireza12t
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Render review stills

render_stills

Render JPEG stills at chosen seconds to preview a film before a full render, and optionally return a single contact sheet for quicker review.

Instructions

Renders JPEG stills of a film at given seconds, to look at before a full render. Returns the file paths. With sheet=true it also makes one contact sheet and returns it as an image, which is cheaper to look at than many stills.

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": {
      "demo": "<demo>"
    },
    "name": "render_stills"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoQuery string passed to the page as location.search, e.g. 'lang=en&cut=b'.
outNoFolder for the stills. Default <demo>/stills.
demoYesFolder that holds the film's index.html (absolute path, or relative to the library root).
sizeNoFrame size WxH, even numbers. Default 1920x1080; 1080x1920 for a vertical Short.
rangeNostart:end:step in seconds, e.g. "0:30:5".
sheetNoAlso make a contact sheet (needs the Python environment) and return it inline.
timesNoSeconds to render, e.g. [0, 2.5, 10].
sheet_colsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the return value (file paths) and that sheet=true returns an inline image and requires the Python environment, but it never states that the tool writes files to disk, whether existing stills are overwritten, or what happens on failure.

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?

Three short sentences, front-loaded with the core action and return value, then the optional contact-sheet behavior. Every clause carries information; nothing is padding.

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 an 8-parameter tool with no output schema and no annotations, the description covers the essential outcome (file paths) and the notable optional mode (contact sheet). The remaining gap is the on-disk write side effect and overwrite behavior, which the schema does not cover either.

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 already 88%, so the baseline is 3, and the description adds real meaning beyond it by explaining what sheet=true produces (one contact sheet returned as an image) and why it is preferable to many stills. It does not touch range/times/size semantics, which the schema already handles.

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 and resource ("Renders JPEG stills of a film at given seconds") plus the return value (file paths), and the phrase "before a full render" implicitly separates it from render_video. It stops short of naming the sibling outright, so an agent must infer the boundary.

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?

"to look at before a full render" gives a clear usage context and the sheet=true note explains a cheaper alternative for reviewing many frames. There is no explicit when-not or a named alternative tool, which keeps it below a 5.

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