Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

transpose_clip

Destructive

Shift MIDI notes or audio pitch in a clip by a given number of semitones, with optional arrangement targeting.

Instructions

Transpose a clip: MIDI notes are moved; audio clips get their pitch shifted.

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_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
semitonesYes
clip_indexYes
arrangementNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the agent knows this mutates state; the description complements them by explaining what changes differently for MIDI versus audio clips. However, it omits important behavioral facts for a destructive operation: whether the change is undoable, whether pitch-shifting preserves warp or timing, and any range limits on semitones.

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?

A single tight sentence that front-loads the action and then splits the behavior by clip type. No filler, though it is arguably too terse for the parameter and behavioral gaps it leaves.

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

Completeness5/5

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

Wrong reasoning anchor: an output schema exists, so return-value explanation is not required, but for a destructive four-parameter mutation with zero schema coverage the description is still incomplete regarding the arrangement flag and reversibility. Score adjusted to reflect that gap rather than assuming completeness from the output schema alone.

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% across four parameters, so the description must compensate and does not. It never explains the track/clip index pair, nor the ambiguity of the 'arrangement' boolean (session versus arrangement clip), which is the single most consequential parameter for locating the right clip.

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?

The description uses a specific verb and resource ('Transpose a clip') and adds a useful distinction between the two domains it acts on: MIDI notes are moved versus audio pitch is shifted. It does not differentiate itself from similar siblings such as transform_clip or quantize_clip, so an agent must infer the boundary, but the core action is unambiguous.

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 guidance on when to use this tool versus alternatives like transform_clip, quantize_clip, or swing_clip, and no stated preconditions. The agent gets no signal about which clip type or context makes this the correct call.

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