Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_scene_activate

Activates a scene for production by creating its frames, audio, and video folders and updating the project stage in project.json.

Instructions

Activate a specific scene for production. Provisions dedicated scenes/scene_XX/ directory with frames/, audio/, and video/ subfolders, and updates project.json stage.

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_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
scene_idYesScene identifier (e.g. 'scene_01').
project_idYesTarget project ID.
scene_titleNoHuman-readable scene title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the meaningful side effects: creation of scenes/scene_XX/ with frames/, audio/, and video/ subfolders, and a mutation of project.json stage. It does not say whether activation is idempotent, what happens if the directories already exist or contain content, or whether the previous stage value is overwritten.

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?

Two sentences, front-loaded with the action and followed by the effects; no filler. It could be slightly tighter by merging the artifact list, but nothing is wasteful.

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 a mutation/provisioning tool with no annotations and no output schema, the description covers the primary effect but omits failure behavior, overwrite semantics, and what the caller gets back on success. An agent knows what it does but not what can go wrong when calling it.

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 coverage is 100%, so the schema already defines all three parameters, and the description adds only indirect meaning (scene_id maps to the scene_XX folder name, project_id maps to project.json). scene_title is never referenced in the description, so nothing beyond the schema is clarified for it.

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 ('Activate a specific scene for production') and immediately qualifies it with the concrete effect (directory provisioning plus project.json stage update). That is enough to distinguish it from graph/directing siblings, though it never explicitly names which sibling handles scene metadata versus activation.

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

Usage Guidelines3/5

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

'For production' implies the activation step precedes frame/audio/video work, which is useful implied context. However, there is no explicit when-to-use versus when-not guidance and no stated prerequisite such as the project needing to exist or the scene needing to be defined first.

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