tdmcp

Create 3D extruded text

create_text_3d

Create a self-contained 3D text scene with extruded glyphs, color, depth, and optional spin, rendered to an image for title cards and animated reveals.

Instructions

Build a self-contained 3D text scene: a Text SOP generates the glyph outlines, an Extrude SOP gives them depth (the depth parameter controls depthscale), and a Geometry COMP holds the pipeline with a Constant MAT for colour. A Camera, a Light, and a Render TOP complete the 3D render, output as a Null TOP. Optional continuous Y-axis spin (spin degrees/sec) is driven by a time expression on the Geometry COMP's ry parameter. Exposes Spin and Depth as live knobs. The classic signature look for title cards, lyric reveals, and 3D text drops — use create_kinetic_text instead for flat 2D animated text. Returns a summary plus a JSON block with the container path, created node 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_text_3d"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Base name for the self-contained container COMP (default 'text_3d').	text_3d
`spin`	No	Continuous Y-axis rotation in degrees per second (0 = static). Driven by an expression on the Geometry COMP's ry parameter.
`text`	No	The text to render in 3D. Use \n for multiple lines.	HELLO
`color`	No	Text material colour as a hex string ('#ffffff' = white). Sets the Constant MAT's colorr/g/b.	#ffffff
`depth`	No	Extrusion depth in geometry units (controls the Extrude SOP's depthscale). 0 = flat polygons, 0.2 = typical title-card look.
`resolution`	No	Render TOP output resolution as [width, height] in pixels (default [1280, 720]).
`parent_path`	No	Parent COMP path where the text-3D container is created (default '/project1').	/project1

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses the exact node chain (Text SOP, Extrude SOP, Geometry COMP, Constant MAT, Camera, Light, Render TOP, Null TOP), the spin expression on ry, and the return format including summary, JSON fields, and inline preview. This is rich behavioral context; only minor omissions (e.g., failure/overwrite behavior) keep it from a 5.

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 efficiently packed—each sentence covers a distinct facet: pipeline construction, spin behavior, live knobs, use cases/alternative, and return value. No redundant phrases, and the primary purpose is front-loaded.

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?

With 7 params and no output schema, the description carries the responsibility of explaining return values and internal behavior. It states the JSON structure (container path, node paths, controls, errors, warnings, preview) and the use-case context, making it complete for effective tool selection and invocation.

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 coverage is 100%, so the baseline is 3. The description adds minimal extra meaning beyond the schema: primarily that Spin and Depth are exposed as live knobs. Other parameter details (depth controls depthscale, spin drives ry) are already present in the property descriptions, so no significant compensation needed.

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 clearly states 'Build a self-contained 3D text scene' and enumerates the full node pipeline, so the verb and resource are specific. It also explicitly distinguishes itself from create_kinetic_text, making sibling differentiation unambiguous.

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 directly names the alternative: 'use create_kinetic_text instead for flat 2D animated text.' It also provides typical use cases ('title cards, lyric reveals, and 3D text drops'), giving agents both when-to-use and when-not-to-use guidance.

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

Deploy Server