Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_scene_directing_set

Define a scene's directing plan by specifying emotional arc, camera style, color palette, lighting, beat sheet, and continuity so production teams can align shots and pacing.

Instructions

Set director explication for a scene: emotional arc, camera style, color palette, lighting setup, beat sheet, and continuity.

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": {
      "project_id": "<project_id>",
      "scene_id": "<scene_id>"
    },
    "name": "cineflow_scene_directing_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
shotsNoList of shot plans.
scene_idYesScene identifier (e.g. 'scene_01').
sluglineNoStandard script slugline (e.g. 'INT. LAB - NIGHT').
beat_sheetNoList of scene beats (action, conflict, resolution).
continuityNoTime of day, weather, character costume/injury/props states.
project_idYesProject identifier.
dramatic_intentNoEmotional arc, camera style, color palette, lighting setup, pacing.

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, yet it never states whether the operation replaces or merges existing directing data, what happens to fields omitted from the call, whether permissions or an active scene are required, or what the response contains. It only lists the categories of data being written.

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 verb and resource front-loaded and no filler. The trailing enumeration is dense but each item maps to a real payload area, so little is wasted.

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 mutation tool with seven parameters, nested objects, no annotations, and no output schema, the description should explain overwrite semantics, prerequisites, and side effects. None of that is present, leaving an agent unable to predict the effect of a call beyond the broad topic.

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 all seven parameters are already documented, and the description's field list largely restates the schema's own wording for dramatic_intent and continuity. It adds no syntax, format, or constraint detail beyond what the schema provides, 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 uses a specific verb ('Set') plus a named resource ('director explication for a scene') and enumerates the content domains covered. An agent can tell it writes scene-level directing metadata, though nothing distinguishes it from siblings like cineflow_scene_graph_update or cineflow_apply_update.

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 when-to-use or when-not-to-use guidance, no prerequisites (does the scene need to exist or be activated first?), and no mention of alternatives such as the scene graph update tool. Usage is only implied by the verb 'Set'.

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