3dBlock Studio

Overview Schema Source Related Servers Discussions Admin

pick_take

Marks a chosen take as final, copies it to a ' - FINAL.mp4' file, and refreshes the thumbnail so the selected cut is ready for publishing.

Instructions

Mark a take as the FINAL (only when the user chooses it). Copies it to " - FINAL.mp4" and refreshes the thumbnail.

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": "pick_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

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It helpfully states that the tool copies the take to '<Title> - FINAL.mp4' and refreshes the thumbnail, but it does not disclose whether an existing FINAL file would be overwritten, whether the operation is reversible, or what permissions are required.

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 compact sentences with zero wasted wording. The key action and its side effects are front-loaded, and the important user-consent condition is included inline.

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 mutation tool with no annotations and no output schema, the description gives a reasonable summary of purpose and side effects. However, it omits important behavioral details such as overwrite behavior, reversibility, and the meaning of the take parameter, leaving the agent without enough context to call it fully confidently.

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%: the slug parameter is described in the schema, but the take parameter is undocumented in both the schema and the description. The description refers to 'a take' without explaining how the integer take parameter identifies or selects it, so it does not compensate for the gap.

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 action on a specific resource: mark a take as FINAL, with concrete side effects (copying to a named file and refreshing the thumbnail). It implicitly distinguishes itself from sibling tools like render_take, qc_take, and open_take, though it does not explicitly name alternatives.

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 parenthetical 'only when the user chooses it' gives a clear condition for when the tool should be used, which is important for a consequential action. It does not name alternative tools or describe the broader workflow, but the usage context is clear and specific.

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