CineFlow Studio

cineflow_project_update_state

Update the canonical project manifest, automatically tracking changes and reporting impact warnings on downstream shots when character appearance changes after generation.

Instructions

Update the canonical Source of Truth (project.json) manifest. Automatically tracks changes and reports impact warnings on downstream shots (e.g. if character appearance is changed after generation).

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

Input Schema

Name	Required	Description	Default
`updates`	Yes	Dictionary of fields to update (characters, locations, notes, style, etc.).
`project_id`	Yes	Target project ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

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 genuine behavior beyond the name: automatic change tracking and impact warnings on downstream shots, with a concrete example ('if character appearance is changed after generation'). It still omits mutation-relevant context such as whether updates are reversible, how conflicts with already-generated assets are handled, and how the warnings are surfaced.

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 tightly written sentences with the core purpose front-loaded and the side-effect note immediately after. The parenthetical example is slightly verbose but earns its place by making the warning behavior concrete.

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 two-parameter mutation tool with no annotations and no output schema, the description covers purpose and side effects reasonably well. It falls short on what the caller actually receives back (how impact warnings are reported) and on merge semantics for the nested 'updates' object, which is the main source of misuse risk.

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% and both parameters are documented in the schema, so the baseline is 3. The description does not add semantics beyond the schema — for example whether 'updates' is a shallow merge or partial replacement, or what happens to fields omitted from the dictionary.

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 and resource ('Update the canonical Source of Truth (project.json) manifest'), which is clear enough to distinguish it from a plain project create or a scene-graph update. It does not explicitly contrast with sibling tools such as cineflow_apply_update or cineflow_scene_graph_update, so sibling differentiation is left to inference.

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?

Usage is implied by 'canonical Source of Truth' — this is the tool for persistent manifest edits — and the downstream-impact note hints at when care is needed. However, there is no explicit statement of when to prefer this over cineflow_apply_update or cineflow_scene_graph_update, and no prerequisites or exclusions are given.

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

Deploy Server