Skip to main content
Glama

Create autopilot

create_autopilot

Build a beat-driven auto-VJ that randomizes controls or cycles cues on each beat interval, letting visuals evolve hands-free.

Instructions

Build a beat-driven auto-VJ: a Beat CHOP + a CHOP Execute DAT that, every N beats, either randomizes a target COMP's numeric controls (a hands-free drift, set by Amount) or cycles through its stored cues — so a set keeps evolving on its own. Live Active/Beats/Amount knobs let you pause or retune on stage. Reuses the tempo clock, randomize_controls and manage_cue mechanisms. Pair with a generated system (or a control panel) as the target.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comp_pathNoCOMP the autopilot drives — its numeric custom controls (randomize mode) or its stored cues (cue mode). Usually a generated system container or a control panel./project1
modeNo'randomize' nudges the COMP's numeric controls toward new random values each trigger (works on any COMP with controls). 'cue' cycles through the COMP's stored cues (needs cues from manage_cue).randomize
beatsNoFire an action every N beats (4 = once per bar at 4/4).
amountNo(randomize) How far to move toward random each trigger: 1 = full scramble, low = gentle drift.
parent_pathNoWhere to create the autopilot engine./project1
Behavior4/5

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

Annotations indicate no destructive or read-only behavior. The description adds context about live knobs, tempo clock reuse, and trigger mechanisms. It does not contradict annotations and provides reasonable behavioral insight, though it could detail performance implications.

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 two sentences and front-loaded with the core concept. The second sentence is somewhat dense but packs useful detail. It is efficient without being overly terse.

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?

No output schema exists, and the description does not explain what the tool returns (e.g., path to created node). While it covers mechanism and usage context, the lack of return value information is a gap.

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 good descriptions for all parameters. The description integrates parameters into the narrative but does not add significant new meaning beyond what is already in 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 uses a specific verb ('build'/'create') and clearly identifies the resource (a beat-driven auto-VJ). It explains the core mechanism (Beat CHOP + CHOP Execute DAT) and distinguishes it from siblings by focusing on automated, beat-triggered control changes.

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 states the tool reuses 'randomize_controls' and 'manage_cue' mechanisms and pairs with a generated system or control panel. It implies a use case (evolving visuals) but does not explicitly specify when not to use it or what alternatives exist.

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