Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_project_create

Create and initialize a cinematic project in CineFlow Studio, saving its title, screenplay, style, and aspect ratio to the database and storage directory.

Instructions

Initialize a new cinematic project in the studio database and storage directory.

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>",
      "screenplay": "<screenplay>"
    },
    "name": "cineflow_project_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoVisual aesthetic style (e.g. 'cinematic', 'anime', 'documentary').
titleYesProject title.
aspectNoTarget video aspect ratio.
screenplayYesFull screenplay or story synopsis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutating tool. It does disclose that state is written to both the database and a storage directory, which is useful, but says nothing about required permissions, reversibility/cleanup, failure modes, or what is returned on success.

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 well-formed sentence with the action and both side effects front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than disciplined trimming of a richer description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, two-required creation tool with no annotations and no output schema, the definition leaves too much open: the relationship to cineflow_project_init, whether the call is idempotent, and what identifier the agent gets back to use with cineflow_project_get_state are all unstated.

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%, including an enum for aspect and per-field descriptions for title, screenplay and style, so the schema already does the semantic work. The description adds no meaning beyond it, so the baseline 3 applies.

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 names a specific verb ("Initialize") and resource ("a new cinematic project") and even states the two persistence targets, so the agent knows what is being created. It does not, however, distinguish itself from the near-identically named sibling cineflow_project_init, leaving a real ambiguity about which creation entry point to pick.

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?

There is no guidance on when to use this instead of cineflow_project_init or cineflow_project_get_state, no stated prerequisites such as authentication or an existing studio, and no note on what happens if a project with the same title already exists. The agent must infer all routing decisions.

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