Skip to main content
Glama
Sign In
ableton-mcp

ableton-mcp

by jpoindexter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

transpose_notes

Transpose all notes in a selected Ableton Live clip by a given number of semitones, shifting pitch up or down.

Instructions

Transpose all notes in a clip.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • semitones: Number of semitones to transpose (positive = up, negative = down)

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>",
      "semitones": "<semitones>"
    },
    "name": "transpose_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
semitonesYes
clip_indexYes
track_indexYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the burden of disclosing behavioral traits. It merely states the operation without mentioning side effects, reversibility, or whether it applies only to MIDI clips, which is a significant gap 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?

The description is a single front-loaded sentence followed by a clean parameter list. There is no redundancy or fluff, making it efficient and well-structured.

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?

For a simple 3-parameter MIDI operation, the description is sufficient to identify the clip and transposition amount. It omits return values, but since no output schema exists and the operation is straightforward, this is not critical. It could mention that it applies to MIDI notes, but it's adequately complete.

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

Parameters5/5

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

The schema has zero description coverage, and the description fully compensates by explaining each parameter in detail: track_index, clip_index, and semitones (including positive/negative direction). This adds substantial meaning beyond the bare 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 clearly states the action: 'Transpose all notes in a clip.' This is specific and distinguishes it from sibling tools like set_clip_pitch (clip-level pitch) and quantize_clip_notes (timing-based processing).

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus the many related sibling tools. The description only explains parameters, not usage contexts, exclusions, or alternatives.

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