Skip to main content
Glama

set_groove_params

Adjust a Groove Pool groove's timing, random, velocity, and quantization amounts plus the global groove amount in Ableton Live.

Instructions

Adjust a groove in the Groove Pool (amounts in %, as in Live) and/or the global Groove amount (0-1.3, i.e. 0-130 %).

Parameters:

  • groove_index: Groove to change (from get_groove_pool)

  • timing_amount / random_amount / velocity_amount / quantization_amount: New amounts

  • global_amount: Global Groove amount

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": "set_groove_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
groove_indexNo
global_amountNo
random_amountNo
timing_amountNo
velocity_amountNo
quantization_amountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden alone; it does disclose the unit conventions ('amounts in %, as in Live') and the global range (0-1.3, i.e. 0-130%), which prevents obvious misuse. It does not say whether omitted parameters leave values unchanged or reset them, nor whether changes are persistent or undoable.

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 core behavior and unit conventions are front-loaded in the first two sentences, followed by a compact bullet list mapping each parameter. Nearly every line earns its place; only the bullet names repeat labels already visible in the schema.

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?

For a six-parameter mutation tool with no annotations, the description covers units, ranges, and the index source, and it need not explain return values since an output schema exists. It is still incomplete on what happens when all parameters are omitted and on persistence/undo semantics, which matter for a mutation tool with zero annotation coverage.

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 does: all six parameters are named and given meaning, including the % unit convention for the four groove amounts and the 0-1.3 range for global_amount plus the source of groove_index. It stops short of explaining null/omitted behavior or whether amounts are absolute or relative.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (adjust) and resource (a groove in the Groove Pool and/or the global Groove amount), which is distinguishable from set_clip_groove by the mention of Groove Pool editing. It does not explicitly name the sibling it is not, so it stops short of full differentiation.

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 parenthetical 'from get_groove_pool' tells the agent where groove_index comes from, which is a useful sequencing hint. However, it never says when to use this versus set_clip_groove or what happens if no parameters are supplied, so usage is only implied.

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