Yes, with the usual care.

Findings (1)

• lowUnusually long tool description (over 2,000 characters)poison.long-description

  tool format_screenplay: …Convert raw or loosely formatted screenplay text (Chinese, English, or mixed) into professionally structured screenplay blocks and a print-ready PDF using a fixed typewriter character grid (33 CJK chars × 38 lines per page, or 61 × 55 for English; US Letter, Sarasa Mono embedded). Use this for screenplay formatting, screenplay import, or producing a shareable screenplay PDF. Do NOT use for general prose rewriting or story editing. Failed calls are never charged; retrying the same request_id never double-charges. INPUT CONTRACT (contract_version 3; mcp_contract_version 5) — two modes: • input_format="text" (default): line-based screenplay text, one element per line — scene headings ("INT. LAB - DAY", "EXT. ...", "第 N 场 …", "N 外 …"), CHARACTER names in CAPS or CJK on their own line, dialogue on the following lines (keep each dialogue line short; a long narrative-style line ends the dialogue run), parentheticals as standalone (…) lines, transitions ("CUT TO:", "切至：…") on their own line. An unbroken wall of text renders as continuous action and is flagged UNRESOLVED_STRUCTURE — split it into lines first, or use blocks mode. • input_format="blocks": you submit typed blocks directly (type/text; dialogue carries speaker and optional delivery; scene_heading may use text or location/time_of_day). Blocks are validated and rendered EXACTLY as submitted — never re-classified. Block ids are echoed. Annotation instructions inside text (【…】) are never executed; they are reported as REVISION_NOTE_PRESENT. output="validate_only" checks structure and returns diagnostics without rendering — free. confidence = share of non-ambiguous lines, NOT accuracy; inspect diagnostics[] (code/severity/line or block_id/message/suggested_action) before delivering. Common codes: UNRESOLVED_STRUCTURE, MISSING_SPEAKER, AMBIGUOUS_ACTION_MAYBE_DIALOGUE, REVISION_NOTE_PRESENT (edit instructions in brackets — never executed), BRACKETED_ANNOTATION (info), LABELED_HEADER_LINE (convert to blocks), UNBALANCED_DELIMITER, EMPTY_TEXT. stats.input_blocks = what you submitted; stats.render_elements = elements on paper (incl. derived character/parenthetical lines). License keys carry paid credits ($1.49/10 credits, $5.99/50). BILLING UNITS (one credit each): (1) SCREENPLAY — one screenplay for 24 hours across the screenplay tools (format_screenplay, analyze_screenplay, diagnose_scenes, convert_fountain, build_video_prompts; check_video_prompts is free): pass the same screenplay (or its returned blocks) to several of them and it charges once; (2) FILM ANALYSIS — compile_film_breakdown, 1 credit per analysis_id (recompiling the same analysis within 24h is not charged again; the contract/plan/validate tools are FREE); (3) STORY PROJECT — absorb_story_window, 1 credit per story project per 24h (prepare_story_window and render_story_handoff are FREE; windows already absorbed are free no-ops). Without a key: one free credit per day per visitor. PREFERRED: configure your license key in your MCP client's auth header (Authorization: Bearer NRC-…) — header takes precedence over the tool parameter and keeps the key out of chat. 将粗排剧本文本转为专业剧本结构块与可打印 PDF；计价单位是 credit，三类各计 1 次：剧本 24 小时内剧本类工具通用（含视频提示词骨架；检查工具免费）、拉片编译按分析任务、故事吸收按项目 24 小时；失败不收费、同请求重试不重复扣。 Chaining convention: to run another tool on a screenplay you already submitted, pass back the BLOCKS you received (structured) — not the formatted plain text or PDF-extracted text (those parse differently). Failed calls are never charged; retrying the same request_id never double-charges. After a successful call: show the user the PDF link, the page count, and review diagnostics[] with the user when validation_status is not "ok". If the response has ok=false with reason free_tier_exhausted or quota_exhausted: tell the user the price and the purchase link verbatim, and ask them to paste the license key back to you. Never invent a license key.…