Skip to main content
Glama

Narracore Screenplay Formatter

Fountain ⇄ blocks converter

convert_fountain

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). One credit covers one screenplay for 24 hours across the screenplay tools — converting and then formatting the same screenplay charges once. Failed calls are never charged. 剧本块与 Fountain 格式互转;同一份剧本 24 小时内多工具只扣一次。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoto_fountain only: raw screenplay text (input_format="text")
blocksNoto_fountain only: typed blocks (input_format="blocks")
fountainNofrom_fountain only: the Fountain source text
directionYesto_fountain: screenplay → Fountain text. from_fountain: Fountain text → typed blocks.
request_idNoIdempotency key (optional)
license_keyNoLicense key NRC-XXXX-XXXX-XXXX-XXXX (optional — free daily quota works without one)
input_formatNoto_fountain only: screenplay source format

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
toolNo
stateNo
statsNo
blocksNo
reasonNo
creditsNo
messageNo
fountainNo
recoveryNo
warningsNo
conflictsNo
directionNo
next_stepNo
request_idNo
diagnosticsNo
next_actionsNo
contract_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "blocks": {
      +      "items": {
      +        "additionalProperties": {},
      +        "properties": {
      +          "delivery": {
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "string"
      +          },
      +          "location": {
      +            "type": "string"
      +          },
      +          "scene_number": {
      +            "type": "string"
      +          },
      +          "speaker": {
      +            "type": "string"
      +          },
      +          "text": {
      +            "type": "string"
      +          },
      +          "time_of_day": {
      +            "type": "string"
      +          },
      +          "type": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "type"
      +        ],
      +        "type": "object"
      +      },
      +      "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"
      +    },
      +    "direction": {
      +      "type": "string"
      +    },
      +    "fountain": {
      +      "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"
      +    },
      +    "state": {},
      +    "stats": {},
      +    "tool": {
      +      "const": "convert_fountain",
      +      "type": "string"
      +    },
      +    "warnings": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "ok"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / blocks / items / properties / text / maxLength
      Added value: +200000
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare safety flags (readOnly=false, idempotent=false, destructive=false), so the description carries the burden and does so richly: Latin upper-casing, CJK preservation, [[…]] notes, boneyard stripping with reporting, skipped title-page/section headers with warnings, and the Chinese-parser fallback. It also discloses the credit model (one credit per screenplay/24h, failed calls never charged), which is genuine behavior beyond the schema.

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?

It is a single dense paragraph rather than a structured layout, but it is front-loaded with the core purpose and nearly every sentence carries distinct information about casing, parsing, fallbacks, or billing. Only the trailing billing clause is slightly redundant against the shorter Chinese restatement.

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?

For a 7-param, bidirectional converter with an output schema, the description covers both directions, edge cases (boneyard, title page, CJK fallback), idempotency/request_id usage, and billing. Nothing an agent needs to invoke it correctly is missing, and return values are left to the output schema.

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 goes beyond it by clarifying direction semantics (to_fountain vs from_fountain), which inputs (text/blocks vs fountain) belong to which direction, and what input_format selects, adding meaningful constraint context.

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?

The description states a specific bidirectional verb+resource: converting between Narracore screenplay blocks and Fountain plain-text. Both directions are named and the relationship to the sibling format_screenplay is made explicit, so an agent can distinguish it 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?

It explains when each direction applies and that from_fountain output can be passed straight to format_screenplay (input_format="blocks"), which is real routing guidance. It does not, however, explicitly say when not to use this tool versus other screenplay siblings like analyze_screenplay.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.