Skip to main content
Glama
Sign In
CineFlow Studio

CineFlow Studio

by MilayaMariyaAi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

cineflow_scene_graph_update

Update a Directed Scene Graph by defining scene nodes, narrative transitions (CUT, CROSSFADE, L_CUT, J_CUT, SMASH_CUT), and montage timeline order to control story flow and continuity.

Instructions

Update the Directed Scene Graph: nodes, transitions (CUT, MATCH_CUT, CROSSFADE, L_CUT, J_CUT, SMASH_CUT), and timeline sequence.

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

Input Schema

NameRequiredDescriptionDefault
edgesNoList of narrative transitions between scenes with carryover state.
nodesNoList of scene node definitions with dramatic intent and continuity.
project_idYesProject identifier.
timeline_sequenceNoOrdered sequence of scene IDs for montage.

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?

With no annotations, the description carries the full behavioral burden for a mutation tool, yet it never says whether omitted fields are preserved or cleared, whether existing nodes are replaced, or what permissions/confirmation are needed. The enumerated transition kinds (CUT, MATCH_CUT, CROSSFADE, L_CUT, J_CUT, SMASH_CUT) add useful domain vocabulary, but the destructive semantics remain undisclosed.

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 front-loaded sentence with the resource named first and the mutated components listed after, with zero filler. It is dense and well-organized; the only shortfall is that the compressed phrasing leaves behavioral questions unaddressed.

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 mutation tool with no annotations and no output schema, the definition is too thin: it omits merge/replace behavior, error conditions, and what the response contains. An agent could call it, but not confidently predict the effect on existing graph data.

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 baseline is 3; the schema already defines nodes, edges, project_id, and timeline_sequence. The description does add genuine meaning by enumerating valid transition types, which the schema does not enumerate, but it says nothing about how carryover state or dramatic intent fields behave.

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?

States a specific verb ('Update') and resource ('Directed Scene Graph') and enumerates the three things it mutates: nodes, transitions, and timeline sequence. This clearly contrasts with the read-only sibling cineflow_scene_graph_get, but the description never names that sibling or explicitly scope the difference.

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 guidance, no prerequisites, and no statement about whether this is a full replacement or a partial update (only project_id is required). An agent must infer from the tool name that it should prefer cineflow_scene_graph_get for reads; nothing in the text routes it.

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