Skip to main content
Glama
Pantani

tdmcp

by Pantani
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

Create slit-scan

create_slit_scan

Creates a slit-scan visual system in TouchDesigner that maps time to space by sampling rows or columns from a ring buffer of past frames. Works headlessly with a synthetic noise source when no camera is available.

Instructions

Build a slit-scan visual system: each row (or column) of the output samples a different past frame from a Cache TOP ring buffer, producing the classic 'time-as-space' stretched-time look (Floris Kaayk / Adam Magyar style). Creates a new baseCOMP under parent_path holding a source TOP, a Cache TOP ring buffer, a slit GLSL shader, and a Null output. When no source_top_path is given, a synthetic Noise TOP is used so the tool works headless / on CI without camera permission. Exposes a live 'Depth' knob. Note: GLSL compile is UNVERIFIED offline; cacheTOP 2D-array binding must be validated live in TouchDesigner. Memory cost at 1080p RGBA16 is ~depth × 32 MB; depth 600 ≈ 5 GB VRAM. Output freezes when the timeline is paused (cacheTOP stops recording — expected behaviour). Returns a summary plus a JSON block with the container path, created node paths, output path, exposed controls, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent network where the slit-scan container is created (default '/project1')./project1
nameNoContainer name for the slit-scan system (default 'slit_scan').slit_scan
source_top_pathNoOptional path to an existing TOP to scan (e.g. '/project1/videodevicein1'). When omitted a synthetic noiseTOP seed is created inside the container so the tool runs headless / on CI without camera permission.
cache_depthNoNumber of frames stored in the Cache TOP ring buffer (1–600, default 60). Memory cost: ~depth × W × H × 16 B at RGBA16. At 1080p, 600 frames ≈ 5 GB VRAM.
axisNoScreen axis that carries time. 'y' = each row is a different past frame; 'x' = each column (default 'y').y
directionNoWhich end of the axis is 'now'. '+y' = bottom row is the latest frame, top is oldest; '-y' reverses it. Must be compatible with axis (default '+y').+y
expose_controlsNoWhen true (default), expose a live 'Depth' knob on the container bound to cache.cachesize.

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by detailing the creation of a baseCOMP, the dependency on Cache TOP ring buffer, the unverified GLSL shader, memory cost formula, and the expected freeze behavior. This is comprehensive behavioral disclosure, with no contradiction to annotations.

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 a single paragraph that efficiently conveys purpose, operation, edge cases, and warnings. Each sentence earns its place, and it is front-loaded with the key idea. No unnecessary words.

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?

For a complex tool with 7 parameters and no output schema, the description provides full context: what is created, how it works, headless fallback, memory implications, freeze behavior, and the return format (summary with JSON and preview). It is complete.

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% with parameter descriptions. The tool description adds context on the slit-scan effect but does not enhance per-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's purpose: building a slit-scan visual system with a specific visual effect (time-as-space stretched-time), naming references (Floris Kaayk / Adam Magyar style), and detailing the components created (source TOP, Cache TOP ring buffer, slit GLSL shader, Null output). This distinguishes it from other creation tools.

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 usage guidance by explaining headless/CI behavior when no source_top_path is given, memory cost warnings, and the expected freeze when timeline is paused. However, it does not explicitly compare with alternatives like create_time_echo or other time-based effects among siblings, limiting usage differentiation.

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