Skip to main content
Glama

Create POP geometry

create_pop_geometry

Create procedural POP geometry by building a SOP chain from primitive to render, with optional subdivision and noise displacement, and expose control knobs.

Instructions

Procedural Op Pattern (POP) geometry generator: build a SOP chain inside a Geometry COMP — primitive (box/sphere/tube/torus/grid/line/text) → Transform SOP (translate/rotate/scale) → optional Subdivide SOP → optional per-point Noise SOP displacement → Material SOP (Constant MAT) → Null SOP — then render through a Camera + Light + Render TOP to a Null TOP. Creates a new baseCOMP under parent_path. Exposes a RotateY control; NoiseAmount + NoisePeriod are exposed only when noise_amount > 0 (otherwise the Noise SOP is omitted and those knobs would be inert). Use build_sop_geometry for a fully declarative SOP chain without a render rig; use create_3d_scene for instanced primitives, create_pbr_scene for PBR shading.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
primitiveNoBase geometry primitive. Each maps to its stock SOP (boxSOP/sphereSOP/tubeSOP/torusSOP/gridSOP/lineSOP/textSOP).box
translateNoTranslation [tx,ty,tz] applied via a Transform SOP after the primitive.
rotateNoRotation [rx,ry,rz] in degrees applied via the same Transform SOP.
scaleNoPer-axis scale [sx,sy,sz] applied via the same Transform SOP. [1,1,1] = unchanged.
subdivisionsNoOptional subdivision count. When > 0 a Subdivide SOP runs after the Transform SOP at this depth, then a per-point Noise SOP works on the denser mesh.
noise_amountNoDisplacement amount of the per-point Noise SOP (0 = bypassed; ~0.1..1 typical for organic warp).
noise_periodNoSpatial period of the displacement noise. Larger = wider/softer ripples; smaller = tighter detail.
text_stringNoWhen `primitive` is 'text', the string fed into the textSOP. Ignored for other primitives.tdmcp
expose_controlsNoWhen true (default), expose live knobs on the container: RotateY always, plus NoiseAmount + NoisePeriod only when noise_amount > 0 (otherwise the Noise SOP is omitted and exposing the knobs would be inert).
base_nameNoOptional base name for the container (defaults to 'pop_geometry'). Final container path is `<parent_path>/<base_name>` with TD's auto-suffix.
parent_pathNoParent network where the POP geometry container is created (default '/project1')./project1
Behavior5/5

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

The description explains side effects: creates a new baseCOMP under parent_path, conditionally exposes controls (NoiseAmount and NoisePeriod only when noise_amount > 0), and omits the Noise SOP when noise_amount=0. Annotations (destructiveHint=false, openWorldHint=true) are consistent and complemented.

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 detailed but slightly long; however, every sentence provides value and it is front-loaded with the core purpose. Could be slightly more concise, but effectively communicates complexity.

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 11 optional parameters and no output schema, the description covers the creation process, conditions, and behavior. It doesn't mention error handling or path existence, but for a creation tool, it is quite complete.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds crucial context: conditional knob exposure, inert parameters when noise_amount=0, and the text_string being ignored for non-text primitives. This goes beyond the schema descriptions.

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 'Procedural Op Pattern (POP) geometry generator' and details the exact SOP chain and render pipeline, distinguishing it from sibling tools like build_sop_geometry and create_3d_scene.

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?

Explicitly provides when to use this tool vs. alternatives: 'Use build_sop_geometry for a fully declarative SOP chain without a render rig; use create_3d_scene for instanced primitives, create_pbr_scene for PBR shading.'

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