Skip to main content
Glama

Create depth-driven POP field

create_depth_pop_field

Create a depth-driven GPU POP scatter field from a depth/mask TOP, with displace, emit, or both scatter modes. Auto-sets up MediaPipe segmentation if depth source is omitted.

Instructions

Build a depth-driven GPU POP scatter field: consumes a depth/mask TOP and uses lookup_texture_pop to sample depth for displacement/scatter proxies (and optionally color). When depth_top_path is omitted, auto-spins-up a setup_segmentation MediaPipe chain inside the container and uses its mask Null TOP as the depth source. Scatter modes: 'displace' applies a uniform depth-scale proxy, 'emit' adds an emission-like jitter scatter proxy, 'both' does both. Forward-compatible: pass create_depth_from_2d (Depth Anything, W4) output as depth_top_path. NOTE: POPs are Experimental — op types and par names are fail-forward, probe on a live TD. Returns a JSON block with container path, depth source info, controls, warnings, and unverified probe record.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the self-contained container created under parent_path.depth_pop_field
parent_pathNoParent COMP path where the depth-pop-field container is created./project1
depth_top_pathNoAbsolute path of an existing depth/mask TOP (luminance = depth, bright = near by default). When omitted, the tool auto-spins-up a setup_segmentation chain inside the container and uses its mask Null TOP as the depth source. Future W4: pass create_depth_from_2d output here.
particle_densityNoApproximate point count fed to pointgeneratorPOP.numpoints (100–500 000).
scatter_modeNo'displace' = uniform depth-scale proxy on the point cloud; 'emit' = emission-like scatter jitter around the sampled depth field; 'both' = depth-scale proxy + scatter jitter. True depth-weighted birth is unverified.displace
depth_scaleNoMultiplier on the depth-driven displacement amount along +Z for displace/both scatter modes. Exposed as DepthScale knob when that displacement proxy is active.
color_by_depthNoWhen true, copies sampled RGBA into POP Color attribute via a second lookup_texture_pop (near = bright / far = dark).
invert_depthNoTreat dark as near instead of bright. Implemented via Level TOP invert on a proxy feed.
point_sizeNoRender TOP point size, exposed as PointSize knob.
spinNoY-rotation of the field in deg/sec, animated via transformPOP ry expression. Exposed as Spin knob.
resolutionNoRender TOP resolution [width, height].
expose_controlsNoBuild the live artist knobs panel for the active depth field controls.
Behavior5/5

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

The description thoroughly discloses behavioral traits: it consumes a depth/mask TOP, uses lookup_texture_pop, and auto-spins-up a MediaPipe chain. It warns that POPs are Experimental with fail-forward op types, and notes unverified probe for depth-weighted birth. Annotations are readOnlyHint=false, destructiveHint=false, openWorldHint=true, which align; no contradiction.

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 relatively long but well-structured, with a clear front-loaded purpose. Every sentence adds information, though some redundancy (e.g., repeating mode explanations) could be tightened. The experimental warning is important but adds length. Overall effective but not maximally concise.

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?

Given the complexity (12 parameters, no output schema), the description is complete: it explains the tool's purpose, usage scenarios, behavioral details, parameter roles (supported by schema), and specifies the return JSON block (container path, depth source info, etc.). No critical gaps remain.

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 description coverage is 100%, so baseline is 3. The description adds value beyond the schema by explaining the auto-setup behavior for depth_top_path, the experimental note on true depth-weighted birth for scatter_mode, and the return format. This additional context merits a score of 4.

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's purpose: 'Build a depth-driven GPU POP scatter field.' It specifies the resource (depth/mask TOP) and the action (creating a POP field with displacement/ scatter proxies). The description also distinguishes modes ('displace', 'emit', 'both') and mentions forward compatibility, setting it apart from sibling tools like create_pop_field.

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 provides clear context on when to use the tool, including handling of depth_top_path omission and auto-setup of a segmentation chain. It explains scatter modes and when to pass create_depth_from_2d output. However, it does not explicitly exclude alternatives or provide when-not-to-use guidance, limiting the score to 4.

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