Skip to main content
Glama

clyphx_clip

Execute clip actions like renaming, warping, or converting audio to MIDI on a selected track’s clip.

Instructions

Execute a ClyphX Pro clip action on the playing/selected clip of a track. Common actions:

  • CLIP CENT x — Set clip cents

  • CLIP CHOP — Chop clip into equal slices

  • CLIP COLOR x — Set clip color

  • CLIP DEL — Delete clip

  • CLIP DUPE — Duplicate clip

  • CLIP END x — Set end position

  • CLIP EXTEND — Double loop length

  • CLIP GAIN x — Adjust audio clip gain

  • CLIP GRID x — Set fixed grid

  • CLIP LEGATO — Toggle legato

  • CLIP LMODE x — Set launch mode (TRIGGER, GATE, TOGGLE, REPEAT)

  • CLIP LQ x — Set launch quantization

  • CLIP MUTE — Toggle clip mute

  • CLIP NAME "x" — Rename clip

  • CLIP QNTZ x — Quantize notes/warps

  • CLIP SEMI x — Transpose semitones

  • CLIP SIG x/y — Set clip time signature

  • CLIP SPLIT x — Split clip at position

  • CLIP START x — Set start position

  • CLIP TOARR — Copy clip to Arrangement

  • CLIP TODR — Convert to Drum Rack

  • CLIP TOMIDI x — Convert audio to MIDI

  • CLIP TOSIMP — Convert to Simpler

  • CLIP WARP — Toggle warping

  • CLIP WARPMODE x — Set warp mode

  • CLIP VELOCITY x — Set velocity

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackYes
actionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lists actions that include destructive operations (e.g., CLIP DEL) and modifications, but does not detail side effects, prerequisites (e.g., clip must exist), or the exact effect on the clip state. The first sentence clarifies it applies to the playing/selected clip, offering some transparency.

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 a single paragraph with a clear list of actions, making it easy to scan. It is front-loaded with the purpose. While concise, it could be slightly more structured with a brief note on parameter formatting, but overall it wastes no words.

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?

Given the tool's complexity (many possible actions) and a simple schema (2 params, no enums), the description covers the range of actions but omits details on output schema (exists but not described), error handling, or exact parameter syntax. It is adequate for basic use but leaves gaps for precise invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. It lists action examples but does not explain the 'track' parameter (e.g., index numbering, valid range) or the exact syntax for the 'action' string (e.g., case sensitivity, required 'CLIP ' prefix). The parameter meaning is partially inferred but not explicitly defined.

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 explicitly states the tool executes a ClyphX Pro clip action on the playing/selected clip of a track, providing a specific verb and resource. It lists 23 common actions, clearly differentiating it from sibling tools that handle other aspects like tempo, playback, or track management.

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 for modifying clips via listed actions but does not provide explicit guidance on when to use this tool versus alternatives like fire_clip, set_clip_name, or set_clip_looping. No 'when not to use' or contrast with sibling tools is given.

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/ursaayush/ableton-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server