Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

clip_move

Move a clip to a new start beat without altering its length. Provide the clip ID and the desired start position.

Instructions

Shorthand: change a clip's start_beats. Length unchanged.

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": {
      "clip_id": "<clip_id>",
      "new_start_beats": "<new_start_beats>"
    },
    "name": "clip_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes
new_start_beatsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose one important behavioral invariant: the clip's length is preserved. It does not state whether the move is reversible, how it affects snap/arrangement context, or what happens if new_start_beats is out of range, but the provided invariant is meaningful.

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 short sentences, front-loaded with the action and followed by the invariant. No filler.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description is thin: it omits return/error behavior and does not clarify when to choose clip_move over clip_set or clip_resize. The core operation is clear, but the surrounding context an agent needs for reliable selection and invocation is missing.

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 coverage is 0%, so the description needed to compensate, but it only reuses the schema's own term 'start_beats'. It does not define what unit beats are in, whether fractional or negative values are allowed, or how clip_id is resolved. 'Length unchanged' is a behavioral hint rather than parameter documentation.

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?

States a specific verb-resource pair: 'change a clip's start_beats', and adds a key distinction with 'Length unchanged', which separates it from clip_resize and clip_set. Even the 'Shorthand' prefix signals it is a focused convenience operation.

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?

'Shorthand' implies this is a shortcut for a common operation, and 'Length unchanged' suggests when the user wants to reposition without altering duration. However, it never names alternatives such as clip_set or clip_resize, nor gives explicit when-not-to-use conditions.

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