Narracore Screenplay Formatter

Screenplay statistics

analyze_screenplay

Deterministic screenplay statistics from the Narracore analyzer (analyzer_version 1.0, same rules as narracore.cn): a scene list with structured scene headings (scene number / location / time of day / INT-EXT parsed from each heading), per-scene word count, dialogue ratio and action density, a character table (cue count, scenes present, dialogue lines, dialogue chars, share of dialogue), and totals.genko_yoshi manuscript-sheet counts for Japanese competitions (400-character 20×20, 200-character 20×10, Kido-style 20×40 — always confirm the current rules of the competition you are entering). Accepts the same inputs as format_screenplay (input_format="text" or "blocks") — pass the SAME screenplay to both tools: one credit covers one screenplay for 24 hours across the screenplay tools (format / analyze / diagnose / convert / video prompts). When chaining tools, pass back the blocks you received (structured), not the formatted plain text. Failed calls are never charged; retrying the same request_id never double-charges. 剧本确定性统计：场景清单（结构化场景头）、逐场字数/对白占比/动作密度、角色戏份表、日式稿纸枚数三口径；同一份剧本 24 小时内多工具只扣一次。

Input Schema

Name	Required	Description
`text`	No	Raw screenplay text (required when input_format="text")
`blocks`	No	Typed blocks (required when input_format="blocks")
`request_id`	No	Idempotency key (optional)
`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. the blocks returned by format_screenplay).

Output Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	No
`state`	No
`reason`	No
`scenes`	No
`totals`	No
`credits`	No
`message`	No
`recovery`	No
`conflicts`	No
`next_step`	No
`characters`	No
`request_id`	No
`diagnostics`	No
`next_actions`	No
`analyzer_version`	No
`contract_version`	No
`validation_status`	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": {
+    "analyzer_version": {
+      "type": "string"
+    },
+    "characters": {
+      "items": {},
+      "type": "array"
+    },
+    "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"
+    },
+    "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"
+    },
+    "scenes": {
+      "items": {},
+      "type": "array"
+    },
+    "state": {},
+    "tool": {
+      "const": "analyze_screenplay",
+      "type": "string"
+    },
+    "totals": {},
+    "validation_status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

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

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond annotations: analyzer/version determinism tied to a specific rule set, a credit model (one credit covers one screenplay for 24h across five tools), no charge on failed calls, and request_id-based idempotent billing. This resolves the apparent tension with idempotentHint=false by clarifying that only billing is idempotent, not output state.

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?

The capability statement is front-loaded and the billing/chaining rules are packed into dense but useful sentences. It runs long and the trailing Chinese sentence largely restates the English content, which adds length without new information for a single-language reader.

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?

Output schema exists, so return values need no prose explanation, and the description still names the main result sections. Combined with billing, determinism, and chaining guidance, an agent has everything needed to call this correctly alongside format_screenplay.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning on top by explaining that input_format='blocks' is meant to receive blocks returned by a sibling tool and that plain formatted text should not be re-fed during chaining. It does not elaborate on text vs blocks parsing tradeoffs or the license_key/request_id parameters, which the schema already documents.

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+resource (deterministic screenplay statistics) and enumerates concrete outputs: scene list with parsed headings, per-scene word count, dialogue ratio, action density, character table, genko_yoshi counts. It also names a sibling (format_screenplay) whose inputs it shares, so an agent can place it in the tool family without opening the schema.

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?

Gives clear operating context: pass the same screenplay used with format_screenplay, and when chaining, pass back blocks (structured) rather than formatted text. It does not, however, specify when to prefer this over diagnose_scenes or compile_film_breakdown, and gives no explicit exclusions, so it stops short of full alternative routing.

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.