CineFlow Studio

cineflow_project_get_state

Retrieve a project's canonical manifest to check stage, approved characters, active scene, and production history. Use it to sync AI filmmaking state before planning or editing.

Instructions

Read the canonical Source of Truth (project.json) manifest. Returns project stage, approved characters, active scene, and production history.

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

Input Schema

Name	Required	Description	Default
`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

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. 'Read' implies a non-mutating call and the listed return fields help, but it says nothing about permissions/auth, behavior when the project_id does not exist, whether a missing manifest is created, or the response shape beyond a field list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the identity of the resource front-loaded and the return payload immediately after. Nothing should be cut or reordered.

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

Completeness4/5

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

With no output schema, the description correctly compensates by naming the returned fields, and the single required parameter is fully documented in the schema. The only shortfall is missing failure/empty-state behavior for a tool that reads a specific file.

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?

Only one parameter exists and the schema describes it fully at 100% coverage, so the schema already does the work. The description adds no meaning about project_id format, source, or lookup semantics, which is the baseline case for high coverage.

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: 'Read the canonical Source of Truth (project.json) manifest', and enumerates what it returns (stage, approved characters, active scene, production history). This distinguishes it from the write-side sibling cineflow_project_update_state without needing to name it explicitly.

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 only implied — the 'canonical Source of Truth' framing suggests reading current state before mutating it, but there is no explicit when-to-use, no prerequisites, and no mention of alternatives such as cineflow_projects_list or cineflow_project_update_state.

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

Deploy Server