3dBlock Studio

by TheGivingCircuits

Overview Schema Source Related Servers Discussions Admin

Local

read_episode

Read-only

Loads all files of an episode or example (spec.js, scene.js, notes) for use as reference builds.

Instructions

Read every file of an episode or example (spec.js, scene.js, notes). Use the examples as reference builds.

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>"
    },
    "name": "read_episode"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	episode slug, e.g. the-cursed-tape (or an example slug for read-only tools)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that every file of an episode or example is read and names the expected files, but it does not describe return format, pagination, error behavior, or whether file contents are returned directly.

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 two short sentences and front-loads the core operation before adding a usage hint. There is no redundant or filler text.

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?

For a simple one-parameter read tool with complete schema coverage and a read-only annotation, the description supplies the key missing context: which files are read and the episode/example distinction. It could be slightly more complete about the return shape, but no output schema exists and the tool is straightforward.

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%, so the single slug parameter is fully documented in the schema. The description reinforces that the slug may refer to an episode or an example, but it adds no syntax or format details beyond what the schema already provides.

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 states a specific verb and resource: reading every file of an episode or example, and it names the file types (spec.js, scene.js, notes). It does not explicitly differentiate from the sibling read_file tool, which reads individual files, so the sibling distinction is implied rather than stated.

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

Usage Guidelines3/5

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

The description provides a usage hint: 'Use the examples as reference builds,' which suggests a context for reading example slugs. However, it does not state when to use this tool versus read_file or list_episodes, and it gives no exclusions or prerequisites.

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