3dBlock Studio

by TheGivingCircuits

Overview Schema Source Related Servers Discussions Admin

Local

open_take

Open a chosen episode take in the computer's video player to watch the rendered clip for review.

Instructions

Open a take in the computer's video player so the user can watch it.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only states that a video player is opened; it does not disclose whether the take must already exist, whether a local desktop session is required, what happens on failure, or whether the tool returns anything.

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 redundant or wasted language.

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

Completeness3/5

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

For a simple two-parameter tool with no output schema, the core action is clear, but the lack of annotations and undocumented 'take' parameter leave prerequisites and side effects implicit.

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 50%, with the 'take' parameter undocumented. The description does not compensate by explaining the meaning of 'take' or how slug and take combine to identify the video to open.

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 uses a specific verb and resource: 'Open a take in the computer's video player.' An agent can understand the action and target, though it does not differentiate this tool from siblings like list_takes, qc_take, or render_take.

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 phrase 'so the user can watch it' implies the intended use, but the description provides no explicit when-to-use guidance, prerequisites, or alternatives to sibling tools.

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