Skip to main content
Glama

Create feedback tunnel

create_feedback_tunnel

Build an infinite zoom-and-rotate feedback tunnel with audio-bind-ready controls for live performance. Use a seed TOP or built-in noise to create hypnotic inward-spiral visuals.

Instructions

Build a parameterized infinite-zoom/rotate feedback tunnel: a seed TOP is composited with its own fed-back, zoomed, rotated, and decayed frame each cook to produce a hypnotic inward-spiral tunnel. Four audio-bind-ready controls (Zoom, Rotate, HueShift, Decay) are exposed on the container for live performance. A built-in animated noise seed is used when no source TOP is given. The recipe-validated topology (noiseTOP → feedbackTOP + compositeTOP-maximum → transformTOP sx/sy → blurTOP → levelTOP brightness1/huerotate → nullTOP, loop closed by feedbackTOP.par.top) is created inside a new baseCOMP under parent_path. Returns a summary, the container + node paths, exposed controls, any node errors, and an inline preview image. This is the fixed zoom-and-rotate spiral preset; for a general feedback loop with a choice of seed type and an arbitrary ordered chain of effects (blur/displace/edge/…) use create_feedback_network instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNofeedback_tunnel
zoomNoPer-frame zoom factor applied to the fed-back frame (>1 = inward tunnel, e.g. 1.02).
decayNoTrail persistence (0–1). Applied via levelTOP brightness1 each frame. Higher = longer-lived tunnel; default 0.95.
rotateNoPer-frame rotation in degrees added to the fed-back frame (positive = clockwise).
sourceNoPath to an existing TOP to use as the tunnel seed. Omit to generate a built-in animated noise seed.
hue_shiftNoPer-frame hue rotation (0–1, wrapping). Applied via levelTOP huerotate. 0 = no shift.
resolutionNoOutput resolution [width, height] in pixels. Fixed resolution prevents feedback runaway.
parent_pathNoParent COMP path inside which the 'feedback_tunnel' container is created./project1
Behavior5/5

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

Annotations indicate creation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description fully details the created topology, return values (summary, paths, controls, errors, preview), and built-in noise seed behavior. 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?

Description is front-loaded and efficient, but somewhat lengthy with many technical details. Still earns its place without redundancy.

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 no output schema, the description fully covers return values and behavior. Includes topology, controls, live performance context, and alternative usage. Complete for a tool with 8 parameters.

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 88% (high), so baseline 3. Description adds overall context but does not significantly enhance parameter understanding beyond the schema's existing 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?

Description states specific verb+resource: 'Build a parameterized infinite-zoom/rotate feedback tunnel' and distinguishes from sibling tool 'create_feedback_network' by explicitly calling out the fixed preset vs general loop.

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?

Explicit guidance on when to use this tool: 'for a general feedback loop... use create_feedback_network instead.' Also mentions live performance applicability via audio-bind-ready controls.

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