Narracore Screenplay Formatter

Check remaining credits

check_credits

Read-onlyIdempotent

Check the remaining credits for a Narracore license key (NRC-XXXX-XXXX-XXXX-XXXX), plus recent usage and the purchase link. One credit covers one screenplay for 24 hours across the screenplay tools, or one film analysis, or one story project for 24 hours. Costs nothing. 查询授权码剩余服务次数（1 次＝一份剧本 24 小时剧本类工具通用，或一次拉片分析，或一个故事项目 24 小时）。 Preferred: set the key in your MCP client auth (Authorization: Bearer NRC-…) instead of passing it in chat.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`license_key`	No	License key NRC-XXXX-XXXX-XXXX-XXXX (optional if configured in client auth header)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`mode`	No
`used`	No
`limit`	No
`state`	No
`reason`	No
`message`	No
`key_hint`	No
`recovery`	No
`conflicts`	No
`remaining`	No
`request_id`	No
`scope_note`	No
`diagnostics`	No
`purchase_url`	No
`recent_calls`	No
`resets_at_utc`	No
`contract_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": {
+    "conflicts": {},
+    "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"
+    },
+    "key_hint": {
+      "type": "string"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "mode": {
+      "enum": [
+        "key",
+        "anonymous"
+      ],
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "purchase_url": {
+      "type": "string"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "recent_calls": {
+      "items": {},
+      "type": "array"
+    },
+    "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"
+    },
+    "remaining": {
+      "type": "number"
+    },
+    "request_id": {
+      "type": "string"
+    },
+    "resets_at_utc": {
+      "type": "string"
+    },
+    "scope_note": {
+      "type": "string"
+    },
+    "state": {},
+    "used": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}

First observedSep 16, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the bar is lower; the description adds genuinely useful behavior — what a credit actually buys (one screenplay for 24 hours across screenplay tools, one film analysis, or one story project for 24 hours) and that the call is free.

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 and the credit-cost explanation is valuable, but the full Chinese sentence restates the English credit definition verbatim for the same reader, which is duplication rather than added information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 values need no explanation, and the description covers the credit model, the free-call fact, and the auth preference. Complete enough for a zero-required-parameter read tool.

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

Parameters3/5

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

Schema description coverage is 100% and the schema already documents the NRC pattern and the 'optional if configured in client auth header' note, so the description largely repeats it. Baseline 3 applies since the schema carries the parameter semantics.

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 ('Check the remaining credits for a Narracore license key') and enumerates the secondary returns (recent usage, purchase link). No sibling tool does anything comparable, so the agent can distinguish it instantly.

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 invocation context: 'Costs nothing' and the preferred auth method ('set the key in your MCP client auth instead of passing it in chat'). It does not discuss when to call it versus alternatives, but no sibling overlaps, so the guidance that matters is present.

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.