Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

duplicate_clip

Duplicate a MIDI clip from one track and slot to another, even across different tracks, provided both tracks are MIDI and the destination slot is empty.

Instructions

Duplicate a MIDI clip to any other track + slot. Unlike the upstream duplicate_clip_to, this works across tracks. Both tracks must be MIDI tracks; the destination slot must be empty.

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": {
      "src_track": "<src_track>",
      "src_slot": "<src_slot>",
      "dst_track": "<dst_track>",
      "dst_slot": "<dst_slot>"
    },
    "name": "duplicate_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
src_trackYes
src_slotYes
dst_trackYes
dst_slotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description carries burden. Adds constraints but lacks details on operation behavior (e.g., whether source is modified, error handling, or result).

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?

Two sentences, front-loaded with the action, distinguishes from sibling, and lists constraints. No unnecessary 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?

Covers prerequisites and differentiation but misses outcome details (e.g., return value, success indicator) and error handling. Adequate for a simple tool but could be more complete.

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?

Four parameters with 0% schema coverage. Description does not explain parameter semantics beyond naming, leaving interpretation of indexing or ranges to the agent.

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 states 'Duplicate a MIDI clip to any other track + slot' with a specific verb and resource, and explicitly distinguishes itself from the sibling 'duplicate_clip_to' by noting cross-track capability.

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?

Provides clear context for when to use (cross-track duplication) and constraints (both tracks must be MIDI, destination slot empty). Does not explicitly state when not to use, but the alternative is 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