Skip to main content
Glama

Adjust a track

adjust_track

Re-render a track with changes, keeping it musically coherent.

    - length_seconds: fit the track to an exact duration (the engine recomposes the arrangement).
    - turning_point_seconds: add a turning point at that second, where the music changes character
      (new arrangement after the point, an audible transition). Combine with length_seconds to
      lengthen a track and place the turning point in one go. If the track already has a turning
      point, this moves it.
    - ending: how the track ends, "fade_out" or "short" (a stab on the last beat). The track keeps
      its length (or the length_seconds you give) within a quarter of a second either way.
    - time_stretch: tempo factor, for example 0.9 slower or 1.1 faster.
    - pitch_shift: semitones, for example -2 or 3.
    - mute / unmute: stems by name: melody, chords, bass, drums.
    - regenerate: stems to re-pick musical material for (melody, chords, bass, drums); all four
      give a fresh take on the same brief.
    Runs in the background: returns a task_id for wait_for_task.
    

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": {
      "cue_id": "<cue_id>"
    },
    "name": "adjust_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteNo
cue_idYes
endingNo
unmuteNo
regenerateNo
pitch_shiftNo
time_stretchNo
length_secondsNo
turning_point_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the work runs in the background and returns a task_id for wait_for_task, that the engine recomposes the arrangement, that an existing turning point is moved rather than duplicated, and that ending changes keep length within a quarter second. The notable omission is whether the original track is replaced or a new version is produced, which matters for a non-idempotent mutation.

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?

Front-loaded with the one-line purpose, then a scannable bullet per parameter group. Every bullet adds information (units, valid values, combination advice) rather than restating the schema, so length is justified by the nine-parameter surface.

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?

An output schema exists so return values need no explanation, and the description covers nearly all operational behavior for a background mutation. Missing pieces are the meaning of cue_id and whether the original track survives the re-render, which would let an agent call it with full confidence.

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?

With 0% schema description coverage the description must carry the semantics, and it does for eight of nine parameters, including units (seconds, semitones, tempo factor), the enum values for ending, the four valid stem names, and concrete examples like 0.9 or -2. The required cue_id parameter is never explained, which is the one meaningful gap.

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?

"Re-render a track with changes, keeping it musically coherent" gives a specific verb (re-render) and resource (track), and the modifier "with changes" signals this operates on an existing track rather than creating one. It does not explicitly name generate_track as the alternative for new tracks, so differentiation is implied rather than stated.

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?

The description supplies real usage context: it is for altering an existing track, and it explicitly recommends combining length_seconds with turning_point_seconds to lengthen and place a turning point in one go, and notes that specifying all four stems for regenerate yields a fresh take on the same brief. It stops short of stating when not to use it (e.g., when to call generate_track instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.