Narracore Screenplay Formatter

Video prompt scaffolds from screenplay

build_video_prompts

Turn a screenplay into structured video-generation prompt scaffolds (deterministic — no LLM on the server; YOU fill the creative fields). For each selected scene it estimates ~15s segments (marked estimated), registers entities (characters + dialogue counts), proposes ≤4 shots per segment at beat boundaries, pre-fills dialogue lines VERBATIM from the screenplay (never rewrite them), and emits a two-layer template per segment: a SHARED block (A/V limits, camera base, style, entities, causal chain, global guards) written once, plus SHOT blocks carrying only private fields, with CUT-OUT/CUT-IN handoff lines between shots. STYLE GUIDANCE, never a style lock: by default the style section is a decision checklist (medium / frame-rate mechanism / brush / color-domain boundaries / light & face readability / banned vocabulary, each with how-to and example); optionally pass style="engine_cinematic" | "painted_on_twos" | "live_action_neutral" as an EDITABLE starting point, and/or style_note (≤500 chars, passed through verbatim). The response includes a condensed filling guide (eyeline = screen vector, performance arc, causal chain, motion domains, cut-point two-state, targeted negative guards). Estimates are proposals — adjust to the scene's beats. Charged like the other screenplay tools: one credit covers one screenplay for 24 hours across the screenplay tools; failed calls are never charged; same request_id retries never double-charge. After filling, call check_video_prompts (free) for drift findings. 剧本→视频提示词骨架：台词逐字预填、实体登记、段-镜两层结构与切点两态；风格由用户决定（决策清单+可选预设+自由附注），服务端不代做创意决定。

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	Raw screenplay text (required when input_format="text")
`style`	No	Optional style preset as an EDITABLE starting point: engine_cinematic / painted_on_twos / live_action_neutral (default: decision checklist — never a lock)
`blocks`	No	Typed blocks (required when input_format="blocks")
`scenes`	No	Scene numbers (1-based) to scaffold; default all (batch with this when a full screenplay is too large)
`request_id`	No	Idempotency key (optional)
`style_note`	No	Free-form style note (≤500 chars) passed through VERBATIM into every segment shared block — never validated
`license_key`	No	License key NRC-XXXX-XXXX-XXXX-XXXX (optional — free daily quota works without one)
`input_format`	No	text (default): line-based screenplay text. blocks: typed blocks (e.g. from format_screenplay).
`segment_seconds`	No	Target segment duration in seconds (default 15, range 5-60) — estimates, adjust to actual beats

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	No
`guide`	No
`state`	No
`style`	No
`reason`	No
`scenes`	No
`totals`	No
`credits`	No
`message`	No
`recovery`	No
`conflicts`	No
`next_step`	No
`request_id`	No
`diagnostics`	No
`next_actions`	No
`global_entities`	No
`contract_version`	No
`scaffold_version`	No
`style_template_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "conflicts": {},
+    "contract_version": {
+      "type": "string"
+    },
+    "credits": {
+      "additionalProperties": {},
+      "properties": {
+        "bundled": {
+          "type": "boolean"
+        },
+        "charged": {
+          "type": "number"
+        },
+        "free_tier_used": {
+          "type": "boolean"
+        },
+        "note": {
+          "type": "string"
+        },
+        "remaining": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "charged",
+        "remaining"
+      ],
+      "type": "object"
+    },
+    "diagnostics": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "block_id": {
+            "type": "string"
+          },
+          "code": {
+            "type": "string"
+          },
+          "line": {
+            "type": "number"
+          },
+          "message": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "suggested_action": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "code",
+          "severity",
+          "message"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "global_entities": {},
+    "guide": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "next_actions": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "billing": {
+            "enum": [
+              "free",
+              "bundled",
+              "charged"
+            ],
+            "type": "string"
+          },
+          "purpose": {
+            "type": "string"
+          },
+          "requires": {
+            "type": "string"
+          },
+          "reuse_fields": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "tool": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "tool",
+          "purpose",
+          "requires",
+          "billing",
+          "reuse_fields"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_step": {
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "recovery": {
+      "additionalProperties": false,
+      "properties": {
+        "action": {
+          "type": "string"
+        },
+        "field_path": {
+          "type": "string"
+        },
+        "keep_request_id": {
+          "type": "boolean"
+        },
+        "note": {
+          "type": "string"
+        },
+        "resets_at_utc": {
+          "type": "string"
+        },
+        "retry_after_ms": {
+          "type": "number"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "action",
+        "retryable",
+        "keep_request_id"
+      ],
+      "type": "object"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "scaffold_version": {
+      "type": "string"
+    },
+    "scenes": {
+      "items": {},
+      "type": "array"
+    },
+    "state": {},
+    "style": {},
+    "style_template_version": {
+      "type": "string"
+    },
+    "tool": {
+      "const": "build_video_prompts",
+      "type": "string"
+    },
+    "totals": {}
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 19, 2026
- addedInput schema / properties / blocks / items / properties / text / maxLength
```
Added value: +200000
```
AddedSep 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations are minimal (readOnly=false, idempotent=false), so the description carries most of the burden and delivers: determinism, server-side no-LLM behavior, verbatim dialogue preservation, bidirectionality of CUT-OUT/CUT-IN, and a full billing model (one credit/24h, failures not charged, request_id idempotency). It stops short of describing output shape or any rate limits, keeping it out of the top band.

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

Conciseness3/5

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

Purpose and deterministic caveat lead cleanly, but the body is one very long compound sentence packed with parenthetical asides and a bilingual trailer. It is thorough rather than tight; a reader must parse several clauses before reaching the key billing and workflow guidance.

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

Completeness5/5

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

Given 9 parameters, no required fields, complex two-layer output, and an output schema present, the description covers the workflow end-to-end: input modes, entity registration, shot proposal heuristics, style handling, billing, and the next tool to call. Nothing an agent needs in order to invoke it correctly is absent.

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 every parameter carries a description, so the baseline is 3. The description adds meaning beyond the schema for style (editable starting point, never a lock), style_note (verbatim, unvalidated), and segment_seconds (estimates to adjust), but these are restatements of schema intent rather than new syntax this contract provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (turn a screenplay into video-generation prompt scaffolds) and a specific resource, and explicitly distinguishes itself from siblings by describing the two-layer segment/shot output that no sibling (analyze_screenplay, compile_film_breakdown, check_video_prompts) produces. The deterministic/no-LLM clause makes the value proposition unmistakable.

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

Usage Guidelines4/5

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

Explicitly routes the agent forward: 'After filling, call check_video_prompts (free) for drift findings,' and gives the when-to-use condition for style presets vs. the default checklist. It does not, however, state when to choose build_video_prompts over analyze_screenplay or compile_film_breakdown, so the upstream selection is left to inference.

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

All Narracore Screenplay Formatter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.