Narracore Format

convert_fountain

Convert screenplay blocks to Fountain text and parse Fountain back into typed blocks for format_screenplay, handling scene headings, dialogue, transitions, notes, and CJK fallback.

Instructions

Convert between Narracore screenplay blocks and Fountain (the plain-text screenplay interchange format). direction="to_fountain": screenplay (input_format="text" or "blocks") → Fountain text (Latin content upper-cased per convention, CJK preserved verbatim; notes as [[…]]). direction="from_fountain": Fountain text → typed blocks you can pass straight to format_screenplay (input_format="blocks") — supports scene headings (INT/EXT/EST/I/E), character cues with (V.O.)-style extensions (extension becomes the delivery hint), parentheticals, dialogue, TO: transitions, > forced transitions, . forced action, [[notes]]; boneyard /…/ is stripped and reported, title-page keys and # section headers are skipped with warnings; mostly-Chinese content falls back to the Chinese screenplay parser (Fountain rules target Latin scripts). 剧本块与 Fountain 格式互转。Part of the Narracore toolkit — free, local, no account; long-form co-writing at narracore.cn.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	No	to_fountain only: raw screenplay text (input_format="text")
`blocks`	No	to_fountain only: typed blocks (input_format="blocks")
`fountain`	No	from_fountain only: the Fountain source text
`direction`	No	Required, one of to_fountain \| from_fountain: to_fountain = screenplay → Fountain text; from_fountain = Fountain text → typed blocks.
`request_id`	No	Trace id (optional)
`input_format`	No	to_fountain only: screenplay source format

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`tool`	No
`stats`	No
`blocks`	No
`reason`	No
`message`	No
`fountain`	No
`recovery`	No
`warnings`	No
`direction`	No
`next_step`	No
`request_id`	No
`diagnostics`	No
`contract_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: Latin content is upper-cased, CJK preserved verbatim, notes become [[…]], boneyard is stripped and reported, title-page keys and # headers are skipped with warnings, and mostly-Chinese content falls back to a different parser. That is unusually rich disclosure of transformation side effects and failure behavior.

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?

Front-loads the two directions and keeps every technical clause load-bearing, but it is a single dense run-on paragraph mixing English, a Chinese sentence, and a promotional tail ('Part of the Narracore toolkit — free, local, no account…') that does not help tool selection.

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?

An output schema exists, so return structure need not be re-explained, and the description covers the remaining gaps an agent needs: direction semantics, per-direction input requirements, transformation rules, and warning/fallback behavior. Nothing required to invoke 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 already 100%, so the baseline is 3, but the description adds the cross-parameter coupling the schema only states piecemeal: direction selects whether text/blocks or fountain is consumed and which input_format applies. It does not add new format constraints (e.g., maxLength, maxItems) beyond what the schema declares.

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 (convert between Narracore screenplay blocks and Fountain text) and enumerates both directions with their exact source and target types. It also names the sibling it feeds into (format_screenplay) and distinguishes itself from it, so an agent can route without opening schemas.

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?

Clearly states which direction value to pick for each intent and what input each direction consumes, plus the downstream handoff ('blocks you can pass straight to format_screenplay'). It stops short of explicit exclusions or guidance on when a sibling like analyze_screenplay would be preferable.

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

Deploy Server