Narracore Screenplay Formatter

Film protocol contract

get_film_contract

Read-onlyIdempotent

FREE. Return the Narracore Film Contract by section — the protocol that lets ANY vision-capable agent turn its own observation of a film into a stable, comparable, traceable Film IR (shot/scene/relation), validated and compiled by this server. The video NEVER leaves your machine: you observe and reason with your own models, this server provides the shared language and the deterministic toolchain. section="core" (default): pipeline, entities, the window protocol for long takes, observability levels (observed/mixed/inferred), entity-level provenance, limits. "vocabulary": the closed vocabularies + alias table (normalization is exact→alias→reject — no fuzzy guessing). "observation_guidance": the observation prompt template + how to write interpretive fields. "reasoning_guidance": the dramatic-layer/scene/relation prompt + the Q&A playbook for answering questions from the compiled result. "media_recipe": reference ffmpeg recipes (a platform adapter example — not authoritative output). "all": every section in one call — recommended on first contact. 免费下发的影视拉片契约：分类词表、观察/推理提示词、窗口协议、问答 playbook 与备料配方示例（section="all" 一次拿全）。

Input Schema

TableJSON Schema

Name	Required	Description	Default
`section`	No	Contract section to return (default: core; "all" returns every section in one call)
`film_schema_version`	No	Request a specific film schema version (default: current)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	No
`state`	No
`reason`	No
`content`	No
`message`	No
`section`	No
`recovery`	No
`conflicts`	No
`request_id`	No
`diagnostics`	No
`contract_version`	No
`available_sections`	No
`film_vocab_version`	No
`film_schema_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": {
+    "available_sections": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "conflicts": {},
+    "content": {
+      "type": "string"
+    },
+    "contract_version": {
+      "type": "string"
+    },
+    "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"
+    },
+    "film_schema_version": {
+      "type": "string"
+    },
+    "film_vocab_version": {
+      "type": "string"
+    },
+    "message": {
+      "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"
+    },
+    "section": {
+      "type": "string"
+    },
+    "state": {},
+    "tool": {
+      "const": "get_film_contract",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedOct 3, 2026

changedInput schema / properties / section / description

Previous value: -"Contract section to return (default: core)"New value: +"Contract section to return (default: core; \"all\" returns every section in one call)"

changedInput schema / properties / section / enum

Previous value: -[
-  "core",
-  "vocabulary",
-  "observation_guidance",
-  "reasoning_guidance",
-  "media_recipe"
-]New value: +[
+  "core",
+  "vocabulary",
+  "observation_guidance",
+  "reasoning_guidance",
+  "media_recipe",
+  "all"
+]

AddedSep 17, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/non-openWorld, so the safety profile is covered. The description adds genuinely useful context beyond that: it is free, the video never leaves the caller's machine, and the toolchain is deterministic (normalization is exact→alias→reject, no fuzzy guessing). It does not discuss rate limits or response shape, but the output schema exists to cover the latter.

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?

Front-loaded well with 'FREE' and the core action, and the per-section breakdown is informative. However it is dense and the trailing Chinese sentence largely duplicates the preceding English content without adding new information, which weakens conciseness.

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?

With annotations, a full input schema, and an output schema present, the description supplies everything else an agent needs: the purpose of the contract, the meaning of every section, and a first-contact recommendation. Nothing required to call it correctly is missing.

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, but the description goes further by enumerating and explaining each enum value's content (core contents, vocabulary alias table, guidance prompts, media_recipe caveat). The film_schema_version parameter is left to the schema, which is adequate.

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 and resource — 'Return the Narracore Film Contract by section' — and immediately defines what that contract is (the protocol that produces a validated Film IR). An agent can distinguish this documentation/contract tool from siblings like compile_film_breakdown or validate_film_breakdown 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 per-section routing (what each section contains) and an explicit recommendation — section="all" on first contact. It does not state when to prefer this over sibling tools or what to do after retrieving the contract, so it stops short of full when/when-not guidance.

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.