Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

copy_region

Copies a region to a compatible active playlist at a chosen position and target track. MIDI sources fork independently while audio shares its source, with native playlist undo preserved.

Instructions

Copy to a compatible active playlist; fork MIDI source independently; audio shares source; native playlist undo.

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": {
      "request": "<request>"
    },
    "name": "copy_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successNo
warningsNo
revision_afterNo
changed_objectsNo
revision_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior4/5

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

Annotations cover the safety envelope (readOnly=false, destructive=false, idempotent=false), and the description adds real behavior beyond them: MIDI regions are forked into an independent source while audio continues to share the source, and the operation participates in native playlist undo. What it omits is equally notable given the schema — nothing is said about dry_run, confirm_delete, or expected_revision concurrency checking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the action, but it is written as four telegraphic semicolon fragments with no subjects, which hurts scanability. Nothing is wasted, but the density trades clarity for brevity.

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?

An output schema exists so return values need not be described, but for a mutating copy with confirmation, dry-run, and revision-guard parameters and zero schema descriptions, four fragments are not enough. An agent cannot tell what triggers deletion-confirmation or how revisions interact with the copy.

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 a nested request object with nine sub-properties, so the description carries the full burden and largely fails: name, position, track_id, region_id, target_track_id, dry_run, confirm_delete, and expected_revision are never explained. Only 'compatible active playlist' faintly gestures at target_track_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Copy to a compatible active playlist" gives a verb and a target, but 'copy' largely restates the tool name and the object being copied (a region) is never named. The MIDI/audio clauses describe consequences rather than scope, so an agent must infer that a region is copied from one track to another.

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?

The word 'compatible' hints at a precondition but never states it, and there is no guidance on when to use this over move_region or create_midi_region. No exclusions, no prerequisites, no notes on what makes a playlist compatible.

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