CineFlow Studio

cineflow_project_init

Initialize a film project on disk: save the screenplay or book in source/, create project.json as the source of truth, and set up materials/ and scenes/ folders.

Instructions

Initialize a physical project directory tree on disk. Stores original screenplay/book in source/, creates project.json as canonical Source of Truth, and provisions materials/ and scenes/ subdirectories.

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": {
      "title": "<title>",
      "source_text": "<source_text>"
    },
    "name": "cineflow_project_init"
  }
}

Input Schema

Name	Required	Description
`style`	No	Visual aesthetic style.
`title`	Yes	Project title.
`aspect`	No	Target aspect ratio.
`scenes`	No	Extracted list of scenes/episodes.
`locations`	No	Extracted key locations.
`characters`	No	Extracted cast list with names and visual descriptions.
`source_text`	Yes	Original text of the screenplay, book chapter, or story.
`source_filename`	No	Filename to store in source/ (e.g. 'book_chapter_1.txt').

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

C2.9/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 disclosure burden. It does name concrete side effects (writes files to disk, creates project.json as canonical Source of Truth), which is credit-worthy, but it says nothing about idempotency, whether an existing directory is overwritten or errors out, required permissions, or failure modes for an operation that writes to the filesystem.

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?

A single sentence, front-loaded with the verb and the primary outcome, with a clean enumerated list of artifacts. No filler, though the second clause packs three separate effects into one long sentence.

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?

For an eight-parameter initializer with no annotations and no output schema, the description covers the filesystem outcome but leaves the optional structural parameters (scenes, characters, locations, style, aspect) unaccounted for. An agent cannot tell whether passing them changes the created tree or just seeds project.json.

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 100%, so the schema already documents all eight parameters and the baseline is 3. The description adds only light mapping (source_text/source_filename land in source/, title drives project.json) and says nothing about how the optional scenes, characters, and locations arrays are persisted.

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?

Names a specific verb ('Initialize') and concrete resource (a physical project directory tree on disk), then enumerates exactly what it produces: source/, project.json, materials/, and scenes/. It is clear what the tool does, though it never distinguishes itself from the sibling cineflow_project_create, leaving the agent to guess which one creates the project record.

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 describes the effect but gives no when-to-use guidance, no prerequisites, and no exclusions. With a sibling literally named cineflow_project_create, the absence of any routing statement is a meaningful gap for a project-setup step.

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

Deploy Server