tdmcp

Controlled disorder grid

controlled_disorder_grid

Generate a grid of quads with a single disorder knob: set 0 for a perfect grid, 1 for full chaos. Adjust per-cell position, rotation, and scale jitter together, and preview directly in TouchDesigner.

Instructions

Generate a rows×cols grid of quads (or outlined cells) with a single order↔chaos disorder knob: 0 = a perfect grid, 1 = full chaos. The one knob scales per-cell position, rotation, and scale jitter together — each hashed from the cell index in a single GLSL TOP so the pattern is stable and reproducible (the classic generative-design 'controlled randomness' / Schotter study, no external source). Set outline: true for line cells. Creates a new baseCOMP under parent_path. Exposes the live Disorder knob plus CellColor/Background swatches. Returns a summary plus a JSON block with node paths, exposed controls, node errors, warnings, and an inline preview image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "controlled_disorder_grid"
  }
}

Input Schema

Name	Required	Description	Default
`cols`	No	Number of grid columns (left to right).
`fill`	No	Cell size within its slot (0..1); leaves gutters between cells.
`rows`	No	Number of grid rows (top to bottom).
`outline`	No	Draw outlined cells instead of filled quads (classic Schotter look).
`disorder`	No	The single order↔chaos knob. 0 = a perfect grid; 1 = full chaos. Scales all per-cell position/rotation/scale jitter together.
`background`	No	Background colour hex. Live RGB swatch 'Background'.	#101014
`cell_color`	No	Cell / line colour hex (e.g. '#f2f2f2'). Live RGB swatch 'CellColor'.	#f2f2f2
`line_width`	No	Outline thickness (fraction of a cell); used only when outline=true.
`pos_jitter`	No	Max per-cell position offset at disorder=1 (fraction of a cell).
`resolution`	No	Output resolution [width, height] of the GLSL TOP (square suits a grid).
`rot_jitter`	No	Max per-cell rotation at disorder=1 (radians).
`parent_path`	No	Parent COMP path the self-contained 'disorder_grid' container is created inside.	/project1
`scale_jitter`	No	Max per-cell scale variation at disorder=1 (fraction).
`expose_controls`	No	Expose the live Disorder knob (and CellColor/Background swatches).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description transparently discloses side effects: 'Creates a new baseCOMP under parent_path', determinism via 'each hashed from the cell index in a single GLSL TOP', and the shape of the return value including node errors and warnings. This goes well beyond the annotations (readOnlyHint: false, openWorldHint: true) by explaining what will be created and what the response contains. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences with no wasted words. The first sentence specifies the core function and the disorder range, and subsequent sentences cover customization, creation side effects, and return value in a compact, front-loaded structure.

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 14 parameters, no output schema, and only basic annotations, the description covers all essential context: what it generates, how it achieves stability, what side effects occur, what live controls are exposed, and exactly what the response includes (summary, node paths, errors, warnings, preview image). The return-value detail compensates for the missing output schema.

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%, so the baseline is 3. The description adds cross-parameter meaning by explaining that the disorder knob 'scales per-cell position, rotation, and scale jitter together', connecting the individual jitter parameters (pos_jitter, rot_jitter, scale_jitter) into a single mental model. It also clarifies parent_path as the creation location. These are meaningful additions 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 leads with a specific verb and resource: 'Generate a rows×cols grid of quads (or outlined cells)' and uniquely identifies the disorder knob. This clearly distinguishes it from generic siblings like create_generative_art or create_glsl_shader.

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

Usage Guidelines3/5

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

The description implies usage context through 'classic generative-design controlled randomness / Schotter study' and explains the single-knob mechanism, but it never explicitly states when to choose this tool over alternatives or names any exclusion cases. Usage is largely implied rather than directed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server