Skip to main content
Glama

Create pixel sort

create_pixel_sort

Sorts pixels by luminance, hue, or saturation within threshold regions to create glitch-art horizontal or vertical streaks. Adjustable mix, iterations, and direction for live tweaking.

Instructions

Build a glitch-art pixel-sort effect that sorts pixels along rows or columns within luminance-thresholded regions, creating the signature Kim Asendorf–style horizontal/vertical streak aesthetic. Uses a multi-pass odd-even transposition sort over a glslTOP feedback chain. Sort key: luminance, hue, or saturation. Exposes Mix, Threshold, Iterations, Direction, and Reset for live tweaking. Defaults to a self-contained noiseTOP source when no input TOP is provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBase name for the created baseCOMP.pixel_sort
parent_pathNoParent COMP path. The pixel-sort container is created inside this path./project1
source_top_pathNoAbsolute path to an existing TOP (e.g. '/project1/movie1'). Pulled in via a Select TOP. If omitted, a self-contained animated noiseTOP source is used (no device permissions).
thresholdNoLuminance gate [0..1]. Pixels with luminance >= threshold are sortable; others are locked in place. Live-tweakable.
axisNox = sort along rows (horizontal streaks), y = along columns (vertical streaks).x
sort_byNoSort key: the channel the odd-even transposition sort compares on.luminance
directionNodescending puts bright/saturated pixels first — the canonical Asendorf look. Live-tweakable.descending
iterationsNoNumber of odd-even sort passes to run via the Feedback TOP. Higher = closer to fully sorted but heavier cook. Live-tweakable.
mixNoBlend between original (0) and sorted output (1). Live-tweakable.
resolutionNoOutput resolution [width, height] in pixels.
Behavior4/5

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

Description adds behavioral context beyond annotations: it creates a component using glslTOP feedback chain, defaults to noiseTOP, and allows live tweaking. Annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) are minimal, so description carries burden well, though it could mention node creation side effects.

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 a single paragraph of 5 sentences, clear and front-loaded with purpose. Could be more scannable with bullet points, but it is concise without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers main algorithm, parameters, and default source, but fails to specify what the tool returns (e.g., a component path or created node). Missing output details reduces completeness.

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 coverage is 100%, baseline 3. Description adds value by summarizing key parameters (Mix, Threshold, Iterations, Direction, Reset) and explaining sort keys (luminance, hue, saturation) beyond schema 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 clearly states the tool builds a glitch-art pixel-sort effect with specific details (rows/columns, luminance threshold, multi-pass sort, sort keys, live tweaking). It distinguishes itself from many sibling tools like create_glitch or create_datamosh by focusing on pixel sorting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description does not provide explicit guidance on when to use this tool versus alternatives. It implies usage for pixel-sort effects but offers no when-not or comparison to siblings like create_glitch or create_kaleidoscope.

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