tdmcp

Create 3D scene

create_3d_scene

Build a renderable 3D scene with geometry, camera, light, and render output. Optionally add instanced copies with spin and scale variation. Expose rotate and zoom for animation.

Instructions

Build a renderable 3D scene: a Geometry COMP holding the chosen primitive (sphere/box/grid), a Camera, a Light, and a Render TOP, output as a Null. Creates a new baseCOMP under parent_path holding all of these — optionally instanced into a grid of instances copies via GPU instancing, with scale_variation for per-copy random sizes and spin for per-copy rotation over time. Exposes RotateY (whole-scene spin) and Zoom (camera distance) knobs. The starting point for 3D visuals — bind RotateY to a tempo ramp or an audio feature to make it move. Use create_3d_audio_reactive instead when you want the geometry driven by sound, or create_pbr_scene for physically-based materials. Returns a summary plus a JSON block with the container path, created node paths, the geometry/camera/render/output paths, exposed controls, any node errors, warnings, and an inline preview image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_3d_scene"
  }
}

Input Schema

Name	Required	Description	Default
`spin`	No	Per-instance spin around Y in degrees/sec (0 = still). Each copy rotates in place over time; needs instances > 1.
`instances`	No	Copies to scatter via GPU instancing on a grid (1 = a single object).
`primitive`	No	Geometry to render.	sphere
`parent_path`	No	Parent network where the 3D-scene container is created (default '/project1').	/project1
`expose_controls`	No	When true (default), expose live RotateY (spin) and Zoom (camera distance) knobs.
`scale_variation`	No	Per-instance size variation: 0 = all the same size, 1 = sizes range from 0 to full. Needs instances > 1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses detailed behavioral traits: what nodes are created (baseCOMP with Geometry, Camera, Light, Render TOP, Null), options like GPU instancing with scale_variation and spin, exposed controls (RotateY, Zoom), and return value details (summary plus JSON block with paths, errors, warnings, preview image). This goes well beyond the minimal annotations (readOnlyHint=false, destructiveHint=false) and adds meaningful context about side effects and output.

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

Conciseness4/5

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

The description is information-dense and well-structured, starting with the core action, then optional behaviors, usage suggestion, alternatives, and return format. It is slightly longer than strictly necessary but every sentence adds value; no filler or redundancy.

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

Completeness5/5

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

The description completely covers the tool's purpose, usage, parameters, side effects, alternatives, and return value in the absence of an output schema. It even informs about node errors and warnings in the return, making it self-sufficient for an AI agent to invoke correctly.

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% with each parameter already having descriptions. The description adds conceptual cohesion by explaining how instances, scale_variation, and spin interact in the scene, and how expose_controls relates to the knobs. While it doesn't add new syntax details, it provides helpful context that ties the parameters together.

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?

The description explicitly states the tool 'Build a renderable 3D scene' and enumerates the exact composition: Geometry COMP, Camera, Light, Render TOP, output as Null. It also names the primitive choices and differentiates from sibling tools by explicitly mentioning create_3d_audio_reactive and create_pbr_scene as alternatives for different use cases.

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

Usage Guidelines5/5

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

The description provides clear when-to-use guidance: it positions the tool as 'The starting point for 3D visuals' and recommends binding RotateY to tempo/audio. It explicitly states 'Use create_3d_audio_reactive instead when you want the geometry driven by sound, or create_pbr_scene for physically-based materials,' giving direct alternative conditions.

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

Deploy Server