3dBlock Studio

Overview Schema Source Related Servers Discussions Admin

new_episode

Create an episode folder from a series template, including a working placeholder scene that renders as-is for immediate setup.

Instructions

Create an episode folder from a series template (a working placeholder scene that renders as-is).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>",
      "title": "<title>"
    },
    "name": "new_episode"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`year`	No
`title`	Yes
`engine`	No	default comes from the series
`series`	No	Guess The Horror, Strange History, Custom, or your own name	Guess The Horror

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses that the output is a placeholder scene that renders as-is, but omits permissions, side effects, overwrite behavior, file structure created, and any constraints on the source series.

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

Conciseness5/5

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

The description is a single, front-loaded sentence with no wasted words. It states the core action and the nature of the created artifact efficiently.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a creation tool with five parameters, no annotations, no output schema, and incomplete schema documentation, the description is too sparse. It does not explain how parameters map to the resulting folder or what an agent should expect after calling it.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description should compensate. It mentions 'series template' hinting at the series parameter, but says nothing about slug, title, year, or engine, and does not clarify required fields or defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource: 'Create an episode folder from a series template.' It also clarifies the result is a working placeholder scene that renders as-is. It does not explicitly name sibling tools, but the creation action is distinct from read/list alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is implied usage – creating a new episode folder from a series template – but no explicit guidance on when to use this versus list_episodes or read_episode, no prerequisites, and no notes about checking for existing episodes.

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