Skip to main content
Glama

set_clip_groove

Apply or remove a Live Groove Pool groove on a session or arrangement clip to adjust timing/swing non-destructively; omit the groove index to clear it.

Instructions

Apply a Groove Pool groove to a clip (Live's own swing/groove engine, non-destructive), or remove it with groove_index omitted.

Parameters:

  • track_index / clip_index: The clip

  • groove_index: Index from get_groove_pool (omit to remove the groove)

  • location: "session" (default) or "arrangement"

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>"
    },
    "name": "set_clip_groove"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
clip_indexYes
track_indexYes
groove_indexNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does deliver a genuinely useful behavioral fact — the operation is non-destructive — plus the removal semantics. It does not say what happens to a groove already on the clip (replace vs stack), whether the call is idempotent, or what error conditions look like, leaving meaningful gaps for a mutation tool.

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?

One front-loaded sentence establishes what the tool does and both modes, followed by a compact parameter list with no filler. Every line is functional and well organized.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers the dual apply/remove behavior plus all four parameters. The remaining gap is mutation edge cases such as overwriting an existing groove or behavior when the clip is not in the specified location.

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 0%, so the description must compensate, and it largely does: it enumerates the allowed values for location ('session' default or 'arrangement'), which the schema does not declare as an enum, and it explains that omitting groove_index removes the groove rather than simply calling it optional. The track_index/clip_index bullet ('The clip') is terse and adds little beyond the property names.

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?

States a specific verb+resource ('Apply a Groove Pool groove to a clip') and even covers the inverse operation ('remove it with groove_index omitted'), so an agent knows both modes without opening the schema. Naming Live's swing/groove engine and 'non-destructive' disambiguates it from siblings like set_groove_params, which edits the groove itself rather than assigning it.

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?

Explicitly tells the agent how to trigger the removal path (omit groove_index) and where groove indices come from (get_groove_pool). It stops short of an explicit contrast with siblings such as set_groove_params or get_groove_pool, so the routing guidance is clear but not fully enumerated.

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

Deploy Server

Other Tools