Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hyperframes_preview

Launches a live preview studio for a Hyperframes project so editors can review media and edits in the browser before export.

Instructions

Launch Hyperframes preview studio for live preview.

Args: project_path: Absolute path to the Hyperframes project directory. port: Port for the preview server (default 3002).

Input Schema

NameRequiredDescriptionDefault
portNo
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
project_pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.4
    • addedInput schema / properties / overwrite
      Added value: +{
+  "default": false,
+  "description": "Explicitly allow replacing existing media. Existing non-media files are protected.",
+  "title": "Overwrite",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.16.0
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.5.1

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions the default port but does not disclose server lifecycle, whether the preview process is long-running/blocking, permission requirements, or the implications of the overwrite parameter for replacing existing media.

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?

The description is short and front-loaded with the main purpose, followed by compact argument notes. It avoids unnecessary filler, though the Args block is somewhat terse and could integrate parameter relevance more cleanly.

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?

The presence of an output schema reduces the need to describe return values, and the description covers the basic launch action. However, for a tool with no annotations and an overwrite option, it omits important operational context such as server lifecycle and replacement behavior.

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 only 33%, so the description should compensate. It usefully clarifies that project_path must be an absolute path and restates the port default, but it completely omits the overwrite parameter, which is the most behaviorally significant input.

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: launch the Hyperframes preview studio for live preview. It is clear what the tool does, though it does not explicitly distinguish it from sibling preview-related tools such as video_preview or hyperframes_snapshot.

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?

The phrase "for live preview" gives implied usage context, but there is no explicit guidance on when to use this versus alternatives like hyperframes_snapshot or hyperframes_capture, nor any exclusions or prerequisites.

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