Skip to main content
Glama

Clip Move

audacity_clip_move
Destructive

Move the audio clip covering a specified time on a track so it starts at a new start time in seconds.

Instructions

Move the clip that covers time at on a track so it starts at start seconds.

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": "<track>",
      "at": "<at>",
      "start": "<start>"
    },
    "name": "audacity_clip_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
atYes
startYes
trackYestrack index (0-based) or unique track name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description adds the useful selection semantic (clip identified by time coverage, not by ID), but for a destructive move it does not say what happens to clips already occupying the target range, whether other clips shift or are overwritten, or what occurs if no clip covers `at`.

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?

A single sentence with the selection rule front-loaded and no redundant wording. Every clause carries information the agent needs to invoke it correctly.

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

Completeness3/5

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

Three required parameters with no output schema, so return values need no explanation. However, for a destructive, non-idempotent mutation the definition leaves out collision/overlap behavior and the no-clip-at-`at` failure case, which an agent would need to call it safely.

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?

Schema coverage is only 33% — `track` is documented but `at` and `start` are not. The description compensates by defining both: `at` as the time the clip currently covers and `start` as the new start time in seconds, which is meaning the schema alone does not supply.

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?

States a specific verb ('Move') and resource ('the clip') plus the exact selection rule: the clip covering time `at` on a track. That addressing scheme implicitly separates it from property-editing siblings like audacity_clip_set, though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer it should call this to reposition a clip in time. There is no statement of when to prefer this over audacity_clip_set or audacity_edit, and no preconditions such as requiring a clip to already exist at `at`.

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