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

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_clip_length

Adjust a clip's duration by moving its end marker to a specified length in beats from the start marker.

Instructions

Resize a clip by moving its end_marker. Length is measured in beats from the clip's start_marker.

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>",
      "length": "<length>"
    },
    "name": "set_clip_length"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes
clip_indexYes
lengthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It transparently explains the mechanism (moving end_marker) and unit (beats from start_marker). However, it omits potential side effects like impact on loop or notes if present.

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 two concise sentences with no filler. Front-loads the action ('Resize a clip') and immediately clarifies the key unit. Every word adds value.

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 tool with no output schema, the description covers core behavior and units. Lacks prerequisites (e.g., clip must exist) and error conditions, but these are minor gaps for this operation.

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?

Despite 0% schema coverage, the description adds critical meaning for the 'length' parameter by specifying its unit (beats) and reference point (start_marker). Track_index and clip_index are self-explanatory from context.

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 explicitly states 'Resize a clip by moving its end_marker', providing a specific verb+resource pair. It clearly distinguishes from sibling tools like fire_clip or delete_clip, which have different purposes.

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 description implies usage for resizing a clip length in beats, but does not provide when-to-use or when-not-to-use guidance. It lacks comparisons to similar tools like set_clip_loop, which may also affect clip length.

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