Skip to main content
Glama

Create displacement warp

create_displacement_warp

Create a displacement-warp stage that warps a source using noise, audio, or a custom map for VJ heat-haze and liquid effects.

Instructions

Build a displacement-warp stage over a source — the 'heat-haze, liquid, audio-pushed pixels' tool for VJ sets. A Displace TOP warps the source image using a second image as a displacement map; the map is driven by one of three modulators: 'noise' (animated Perlin noise — smooth, continuous warp), 'second_top' (your own displacement map via a Select TOP), or 'audio' (audio FFT spectrum converted to a texture via CHOP-to-TOP, so the warp reacts to the music). Without a source the chain builds over a Ramp TOP test gradient and previews standalone. The Displace TOP's weight (displaceweight1) maps to the amount parameter; the Noise TOP translate speed maps to speed. Amount and Speed are exposed as live knobs. Output is a Null TOP. Returns a summary plus JSON with the container path, created node paths, controls, errors, warnings, and an inline preview image. Pairs with extract_audio_features for reactive warp and apply_post_processing to chain with other effects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the container COMP created under parent_path.displacement_warp
parent_pathNoParent COMP path the self-contained displacement warp container is created inside./project1
sourceNoAbsolute path of a TOP to warp (pulled in via a Select TOP so it can live anywhere in the network). Omit to use a built-in Ramp TOP test source so the chain builds and previews standalone.
modulatorNoWhat drives the displacement map. 'noise' (default): an animated Noise TOP whose translate and period are driven by time — produces smooth heat-haze / liquid warp. 'second_top': a Select TOP pointing at `modulator_top` (your own displacement map). 'audio': a CHOP-to-TOP conversion of audio FFT energy — pixels push in proportion to the audio spectrum. The audio modulator requires an audio device or audio file to be active in the project; without one it runs silently at zero energy.noise
modulator_topNo(second_top mode only) Absolute path of a TOP to use as the displacement map. Required when modulator is 'second_top'; ignored otherwise.
amountNoDisplacement strength — maps to the Displace TOP's `displaceweight1` parameter. 0 = no warp; 1 = full-range warp (can tear); 0.05–0.3 are typical VJ values.
speedNo(noise mode) Animation speed of the noise modulator. Scales the time-driven translate on the Noise TOP — higher values produce faster, more turbulent warp.
resolutionNoOutput resolution [width, height] in pixels.
Behavior5/5

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

Annotations show readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds valuable context beyond annotations: it explains that the tool creates a network of nodes (Displace TOP, Noise TOP, etc.), exposes certain parameters as knobs, and returns a summary with JSON and inline preview. No contradictions.

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 thorough but a bit lengthy. It is well-structured with clear technical details, but a few sentences could be trimmed without losing meaning. However, the front loads the core purpose effectively.

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 adequately explains the return value (summary plus JSON with various fields). It also describes the internal chain behavior, preview capabilities, and complementary tools, making the tool's context 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?

The schema has 100% coverage with descriptions for all parameters. The description goes further by explaining what underlying parameters each user-facing parameter maps to (e.g., amount maps to displaceweight1, speed drives noise translate) and gives typical value ranges and effects for the modulator enum values.

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 starts with 'Build a displacement-warp stage over a source' using a specific verb and resource name, and distinguishes the tool by mentioning its pairing with extract_audio_features and apply_post_processing, which are listed as siblings.

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 clearly states the tool is for 'VJ sets' and provides example use cases like 'heat-haze, liquid, audio-pushed pixels'. It implies usage context but does not explicitly state when not to use this tool or mention other 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