Skip to main content
Glama

Create SDF text

create_sdf_text

Raymarch text into a 3D signed-distance-field slab with adjustable depth, rotation, camera, colors, and lighting. Creates a self-contained TouchDesigner network with live controls.

Instructions

Raymarch a text string as a signed-distance-field 3D slab: a Text TOP renders the glyphs to a mask, and a GLSL TOP treats that mask as an extruded distance field (glyph coverage in XY, closed by two Z planes at ±depth/2) so the letters read as solid, lit, rim-highlit 3D volumes that can spin. Distinct from create_sdf_field (primitive CSG only, no text) and create_text_3d (mesh-extruded text SOP) — this is the raymarched distance-field text look. The mask→SDF is approximate (coverage-derived, no external font SDF atlas required) and eased by smoothing. Creates a new baseCOMP under parent_path. Exposes CameraZ/Speed/StepCount/Intensity/Rotate/Fill/Edge/Background controls and previews the output. Returns a summary plus a JSON block with node paths, exposed controls, node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
boldNoRender the seed text bold (thicker glyph coverage).
fontNoFont family for the Text TOP that seeds the glyph mask (must be installed in TD).Arial
textNoThe string to raymarch as SDF text.HELLO
depthNoExtrusion thickness of the raymarched text slab along Z (uDepth).
speedNoAnimation time multiplier (drives uTime). Live 'Speed' control.
rotateNoY-axis rotation speed of the text (radians/s via uRotate * uTime). Live 'Rotate'. Reads 0 when the TD timeline is paused.
camera_zNoCamera distance from the text (uCameraZ). Live 'CameraZ' control.
intensityNoOutput brightness multiplier (uIntensity). Live 'Intensity'.
smoothingNoHow sharply the mask coverage maps to the XY distance field. Lower = crisper edges, higher = softer/rounder.
backgroundNoBackground / miss colour hex. Live RGB swatch 'Background'.#0a0a12
edge_colorNoRim/edge highlight colour hex. Live RGB swatch 'Edge'.#ff5c8a
fill_colorNoLetter body colour hex (e.g. '#ffd34d'). Live RGB swatch 'Fill'.#ffd34d
resolutionNoOutput resolution [width, height] of the GLSL TOP.
step_countNoRaymarch iterations (uSteps). Live 'StepCount'.
parent_pathNoParent COMP path the self-contained 'sdf_text' container is created inside./project1
expose_controlsNoExpose live CameraZ/Speed/StepCount/Intensity/Rotate/Fill/Edge/Background controls.
light_directionNoLight direction, normalised in shader — baked as GLSL constant.
Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds that it creates a new baseCOMP under parent_path, notes the approximate nature of the mask-to-SDF conversion, and lists exposed controls. No contradictions, and it provides useful behavioral context beyond annotations.

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

Conciseness3/5

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

The description is somewhat verbose, listing many controls and details that are already in the schema. It is front-loaded with the core purpose but could be more concise by reducing redundancy.

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?

Given the complexity (17 parameters, no output schema), the description covers purpose, technique, creation behavior, and return information (summary, JSON with paths, preview). It is sufficiently complete for an agent to understand and invoke the tool.

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% (all 17 parameters have descriptions). The description adds a high-level summary of exposed controls but does not significantly enhance parameter understanding beyond the schema. Baseline 3 is appropriate.

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 the tool raymarches a text string as an SDF 3D slab, and explicitly distinguishes it from similar tools create_sdf_field and create_text_3d, making the purpose specific and unambiguous.

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 description names two alternative tools (create_sdf_field, create_text_3d) and explains how this tool differs, providing clear context for when to use it. It does not explicitly state when not to use it, but the alternatives cover that.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server