Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

audio_clip_import

Place an audio file onto a track as a clip, setting its start position, duration, gain, fades, and optional source offset to skip leading silence.

Instructions

Place an audio file as a clip on a track. warp_mode controls time-stretch behavior. Optional clip-level gain (dB), fade in/out (beats), and offset_in_source (beats — skip the first N beats of the source file, useful for trimming silent intros).

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_id": "<track_id>",
      "file_path": "<file_path>",
      "start_beats": "<start_beats>",
      "length_beats": "<length_beats>"
    },
    "name": "audio_clip_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
gain_dbNo
track_idYes
file_pathYes
warp_modeNonone
start_beatsYes
length_beatsYes
fade_in_beatsNo
fade_out_beatsNo
offset_in_source_beatsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose side effects such as whether an existing clip is replaced, whether file validation occurs, or any other potential mutation beyond adding a clip.

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 brief and to the point, using two sentences to convey the core action and optional parameters without unnecessary verbosity.

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 straightforward import operation, the description provides sufficient context for the main parameters and an example use case. It lacks return type or error behavior, but these are not critical for this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Explains warp_mode, gain_db, fades, and offset, but leaves start_beats, length_beats, and name unexplained. With 10 parameters and no schema descriptions, partial coverage limits an agent's ability to use all parameters correctly.

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 clearly states the primary function with a specific verb ('Place') and object ('an audio file as a clip on a track'), distinguishing it from other clip-related tools like midi_clip_add.

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?

Gives a concrete use case for the offset_in_source_beats parameter (trimming silent intros), but does not explicitly state when to prefer this tool over alternatives or mention prerequisites like track existence.

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