Skip to main content
Glama
Sign In
AbletonMCP

AbletonMCP

by juampicosta
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_warp_marker

Lock a sample position to a specific beat by adding a warp marker to an audio clip.

Instructions

Add a warp marker to an audio clip to lock a sample position to a beat position. beat_time: position in beats where you want the sample to land sample_time: position in seconds in the original audio file

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>",
      "slot_index": "<slot_index>",
      "beat_time": "<beat_time>",
      "sample_time": "<sample_time>"
    },
    "name": "add_warp_marker"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes
slot_indexYes
beat_timeYes
sample_timeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only explains the basic function. Missing disclosures on whether the operation is reversible, whether the clip must already be warped, and what happens if markers exist at the same sample position.

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?

Description is two sentences plus parameter notes, no fluff. However, it could be slightly more structured (e.g., grouping parameter descriptions).

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

Completeness2/5

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

With 4 required parameters and no annotation support, the description lacks context on workflow prerequisites (e.g., clip must be in a slot), whether clip must be warped, and what the output schema returns.

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 description coverage is 0%, so the description must compensate. It explains 'beat_time' and 'sample_time' but leaves 'track_index' and 'slot_index' undocumented, failing to specify how they identify the target clip.

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?

Description clearly states the verb ('Add'), the resource ('warp marker to an audio clip'), and the purpose ('lock a sample position to a beat position'). It differentiates from siblings like 'get_warp_markers' (read) and 'quantize_clip' (different operation).

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?

Description implicitly suggests usage when sample timing adjustment is needed, but provides no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no 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