StackFast FractWin Expert Brain

Read CogentCast Production Status

cogentcast_production_status

Read-onlyIdempotent

Read tenant-scoped Work Sample, narration-review, or audiobook-production state; exact hashes; current-vs-historical derivative projection; and Chief Editor/Gemini/ear/paid/publication gates. Private source bodies and blob locations are not exposed. Audiobook Production v1 reuses this five-tool surface: content_type=audiobook_production registers exact manuscript/script/SSML plus provenance, pronunciation, visual/companion, and deterministic-build receipts at zero cost; production.status returns the current derivative and Chief Editor/Gemini/ear/paid/publication gates. Paid canary, full generation, and publication are distinct receipt-gated stages. Uses the existing CogentCast production service; it does not bypass Studio, mint Chief Editor/Robert approval, substitute model output for human authority, publish publicly, or expose credentials.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`package_id`	Yes	ws_, ccnr_, or ccaud_ package identifier.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`result`	No
`gateway_receipt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 30, 2026
- addedInput schema / properties / package_id / description
```
Added value: +"ws_, ccnr_, or ccaud_ package identifier."
```

Changed3 schema fields changedAug 13, 2026

addedOutput schema / oneOf

Added value: +[
+  {
+    "required": [
+      "result"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "ok",
-  "result",
-  "gateway_receipt"
-]New value: +[
+  "ok",
+  "gateway_receipt"
+]

AddedAug 12, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, and the description adds meaningful context beyond that: private source bodies and blob locations are not exposed, paid canary/full generation/publication are distinct receipt-gated stages, and the tool uses the existing CogentCast service without minting approvals or publishing. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main purpose is front-loaded, but the description is overlong for a one-parameter read-only status tool. The aside about 'Audiobook Production v1 reuses this five-tool surface: content_type=audiobook_production registers exact manuscript/script/SSML...' is extraneous for this specific tool and makes the description harder to parse quickly.

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?

Despite verbosity, it is complete for an agent to select and invoke the tool: it names the resource scope, the gate types returned, limitations on what is exposed, and the parameter schema fully documents package_id. With an output schema present, no return-format explanation is needed.

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%, with package_id already described as a 'ws_, ccnr_, or ccaud_ package identifier.' The tool description does not add any new semantic detail about the parameter that the schema does not already provide, so the baseline of 3 is appropriate.

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 opens with a specific verb and scope: 'Read tenant-scoped Work Sample, narration-review, or audiobook-production state; exact hashes; current-vs-historical derivative projection; and Chief Editor/Gemini/ear/paid/publication gates.' This clearly identifies the resource and what the tool reports, distinguishing it from the creation/run/approval sibling tools.

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?

The description conveys clear context: this is the read-only status surface for CogentCast production, returning derivative and gate state. It also states exclusions such as 'it does not bypass Studio, mint Chief Editor/Robert approval... publish publicly, or expose credentials,' which helps an agent know when not to misuse it as a shortcut. However, it does not explicitly name alternative tools or say 'use production_run when you need to generate.'

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

All StackFast FractWin Expert Brain 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.

Resources

Need Help?