3dBlock Studio

Overview Schema Source Related Servers Discussions Admin

render_stills

Generate a contact-sheet render of 30 evenly spaced frames or chosen times for a quick preview before a full take. Poll job_status until the finished job returns the image.

Instructions

Start a contact-sheet render (30 evenly spaced frames, or chosen times) for a quick look before a full take. Poll job_status; the finished job returns the image.

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": "render_stills"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	episode slug, e.g. the-cursed-tape (or an example slug for read-only tools)
`draft`	No	estimate timings, no ElevenLabs
`times`	No	"auto" or comma-separated seconds, e.g. "0.5,3,7.2"

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the load and does well: it discloses that this is asynchronous ('poll job_status') and what the terminal result is ('the finished job returns the image'), which are the two facts an agent needs. It does not mention whether a prior episode/take must exist, cost/latency implications, or whether renders can be canceled or re-run.

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?

Two sentences, no filler; the render scope is front-loaded before the follow-up instruction. Every clause earns its place.

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 an async render job with no output schema, the description supplies the missing return-value and polling guidance. It is slightly incomplete on the draft/estimate parameter and on any prerequisite state, but nothing critical to invoking it correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that the default behavior is 30 evenly spaced frames while the times parameter overrides that with 'chosen times'. That clarifies the intent behind the otherwise terse 'auto or comma-separated seconds' schema text. It does not touch the draft parameter.

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 ('contact-sheet render') with its defining scope ('30 evenly spaced frames, or chosen times'), and implicitly contrasts with the sibling render_take via 'for a quick look before a full take'. An agent can distinguish this from render_take without opening either schema.

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 a clear usage context ('quick look before a full take') and names the required follow-up tool (job_status). It stops short of an explicit 'when not to use' rule or naming render_take as the alternative for final output, leaving part of the routing to inference.

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