Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

hyperframes_init

Scaffold a new Hyperframes project from blank, warm-grain, or swiss-grid templates, with optional video/audio bootstrap, transcription, and Tailwind support.

Instructions

Scaffold a new Hyperframes project.

Args: name: Project name. output_dir: Directory to create the project in. Defaults to current directory. template: Project template (blank, warm-grain, swiss-grid). Default blank. video: Optional source video for project bootstrap. audio: Optional source audio for project bootstrap. skip_transcribe: Skip Whisper transcription during media bootstrap. model: Whisper model for transcription. language: Language code for transcription. tailwind: Add Tailwind CSS browser-runtime support. resolution: Hyperframes canvas resolution preset.

Input Schema

NameRequiredDescriptionDefault
nameYes
audioNo
modelNo
videoNo
languageNo
tailwindNo
templateNoblank
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
output_dirNo
resolutionNo
skip_transcribeNo

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.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavior: three named templates, Tailwind support, resolution presets, and that media bootstrap triggers Whisper transcription (with skip/model/language controls). It never addresses the write-side risks, like what files are created, or what happens when output_dir already exists.

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 leading sentence is front-loaded and the rest is a compact, scannable parameter list with no filler prose. A few lines restate the schema title rather than adding meaning ('name: Project name.'), but overall the length is proportionate to an 11-parameter tool.

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?

An output schema exists, so return values need not be described, and parameter coverage is adequate. For a filesystem-mutating scaffold with zero annotations, though, the description omits directory-existence behavior, overwrite semantics outside the schema, and any required setup, leaving gaps an agent would care about.

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 description coverage is only 9%, so the description has to compensate, and it does: all 11 parameters get a line, and the template argument exposes concrete values (blank, warm-grain, swiss-grid) that the schema lacks. Some entries are thin; 'model: Whisper model for transcription' and 'resolution: Hyperframes canvas resolution preset' give no valid values or examples.

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?

The first sentence gives a specific verb and resource: 'Scaffold a new Hyperframes project.' An agent can see this is project bootstrap, not render or inspect. It never differentiates itself from similar siblings such as video_project_create, video_init_project, or revideo_materialize, so it stops short of a 5.

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

Usage Guidelines2/5

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

The description says nothing about when to use this tool, when not to, or how it relates to video_project_create / video_init_project. An agent has to infer that scaffolding must precede hyperframes_render. The per-parameter defaults help with invocation but are not usage guidance.

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