Skip to main content
Glama

Create POP lines pointcloud (Plexus)

create_pop_lines_pointcloud

Generates a Plexus-style line-web from a point cloud by finding nearest neighbors and rendering connected lines. Provides controls for density, color, and animation.

Instructions

Plexus-style line-web visual built on the POP family. A POP point cloud (auto-generated or sourced) is fed to a Neighbor POP that fills a per-point Nebr array attribute with closest-neighbor indices. A Script SOP converts that index list into deduplicated line primitives, rendered as a Geometry COMP through a Render TOP to a Null TOP — the classic Plexus look without third-party plugins. auto_pattern: 'noise' (default) = pointgeneratorPOP + noisePOP; 'sphere' = spherePOP; 'grid' = gridPOP. count is hard-capped at 8192 (CPU O(N·k) line emission). color_mode: flat | by_distance (warm→cool gradient) | by_neighbor_count (isolation ramp). Exposes live controls: MaxDistance, MaxNeighbors, Spin, PointSize, LineAlpha. POPs are Experimental — par names and Nebr array-attribute survival through poptoSOP are probe-first unverified; result carries extra.unverified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContainer base name; final path uses TD auto-suffix.pop_lines
parent_pathNoParent network for the system container./project1
source_pathNoIf set, must point to an existing POP/SOP that produces a point cloud. When omitted, a point cloud is auto-generated per auto_pattern.
auto_patternNoUsed only when source_path is undefined. noise = pointgeneratorPOP + noisePOP; sphere = spherePOP; grid = gridPOP.noise
countNoApprox point count when auto-generating. Hard-capped at 8192 (line emission is O(N·k) on CPU).
max_distanceNoRadius (POP world units) the Neighbor POP searches for neighbors. Drives Plexus density.
max_neighborsNoPer-point neighbor cap (neighborPOP.maxneighbors). Higher = denser web.
max_linesNoHard cap on emitted line primitives in the Script SOP (after dedupe).
color_modeNoDrives Cd attribute on the SOP. flat = single color; by_distance = per-line gradient; by_neighbor_count = per-point ramp on isolation.flat
colorNoLine color used directly in flat mode, as warm endpoint in by_distance, as dense endpoint in by_neighbor_count.
line_alphaNoConstant MAT alpha; < 1 lets lines additively glow.
spinNoY-axis degrees/sec spin of the whole field via Transform POP ry expression.
point_sizeNoOptional point overlay size rendered in addition to lines. 0 hides points.
resolutionNoRender TOP resolution [width, height].
expose_controlsNoSkip control panel exposure when false.
Behavior5/5

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

Description discloses experimental status, hard cap at 8192 (CPU O(N·k)), and that result carries extra.unverified. Annotations (readOnlyHint: false, destructiveHint: false, openWorldHint: true) are consistent and not contradicted.

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 comprehensive but slightly dense; it front-loads the purpose and follows a logical flow. Minor redundancy could be trimmed, but overall efficient for the 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 15 parameters, no output schema, and complexity, the description covers the pipeline, constraints, and experimental warning. It hints at the output (Geometry COMP, Render TOP, Null TOP) but could be more explicit about what the tool returns.

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?

All 15 parameters have schema descriptions (100% coverage). The description adds value by explaining parameter interactions (e.g., count cap, color_mode drives Cd, max_distance drives density) and constraints beyond the schema.

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 creates a Plexus-style line-web visual using POP family, neighbor POP, Script SOP, and render pipeline. It distinguishes from siblings by specifying the unique technique and visual style.

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 explains the workflow and configurable options, implicitly guiding usage. It warns that POPs are experimental and result carries extra.unverified. However, it lacks explicit when-to-use vs alternatives.

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