Skip to main content
Glama
KyaniteLabs

kinocut

by KyaniteLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

video_project_create

Scaffold a cinematic video project with style, storyboard, and refs folders, creating a structured workspace for organizing video assets and planning production.

Instructions

Scaffold a cinematic video project with style, storyboard, and refs folders.

Args: slug: Project slug using lowercase letters, numbers, hyphens, or underscores. output_dir: Base directory for the projects/ folder. Defaults to the current working directory.

Input Schema

NameRequiredDescriptionDefault
slugYes
overwriteNoExplicitly allow replacing existing media. Existing non-media files are protected.
output_dirNo

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
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 burden. It discloses the folder structure and output_dir default, but does not explain overwrite behavior, what happens if the project already exists, permissions needed, or other mutation safety details.

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 short and front-loaded: the purpose appears in the first sentence, followed by only the argument details that add value beyond the schema. No sentence is wasted.

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 three-parameter scaffold tool with an output schema, the description covers the core creation behavior and two of the three parameters. The remaining overwrite behavior is documented in the schema, so the definition is largely complete, though the lack of annotations means safety context is thin.

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 33%, but the description compensates well for two of the three parameters: it specifies the slug format (lowercase letters, numbers, hyphens, underscores) and explains output_dir as the base directory defaulting to the current working directory. The overwrite parameter is documented in the schema itself.

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 description states a specific verb and resource: 'Scaffold a cinematic video project' and names the folders it creates (style, storyboard, refs). It is clear what the tool does, but it does not distinguish itself from siblings such as video_init_project or hyperframes_init.

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 word 'Scaffold' implies project initialization, but the description gives no explicit when-to-use guidance, prerequisites, or alternative tools. An agent must infer that this is for starting a new project rather than any sibling create/init tool.

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