Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

move_region

Move a region to a new timeline position nondestructively in an Ardour session, with native undo support for safe edits.

Instructions

Move a region nondestructively; named native 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": "move_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.9/5.0
Behavior3/5

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

The description adds value beyond the annotations by declaring the move is nondestructive and recorded in native undo history, which reinforces destructiveHint=false and is genuinely useful context. However, it says nothing about the dry_run, confirm_delete, or expected_revision options in the schema, which are the main behavioral levers an agent would want explained (especially a confirm_delete flag on a move operation).

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

Conciseness4/5

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

A single short clause with no filler and the key property front-loaded after the verb. It is efficient, though the extreme terseness leaves no room for the guidance the tool actually needs.

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 mutation tool with a six-field request object (including a dry-run and a confirm_delete flag) and only four annotations, the description is far too thin; an output schema excuses return-value explanation but not the missing parameter and safety guidance. The agent is left guessing about position formats and preview behavior.

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 six nested properties, so the description must carry the burden and it does not: the four position units (bbt, seconds, samples, quarter_ticks), the dry_run preview, the expected_revision concurrency token, and confirm_delete are all unexplained. 'Move' only vaguely implies a position argument.

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 and resource ('Move a region') plus a meaningful property (nondestructive, native-undoable), so the agent knows exactly what operation occurs. It does not distinguish itself from siblings like copy_region or trim_region, which also touch region placement, so it falls short of a 5.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative; the mention of 'named native undo' hints at reversibility via the undo tool but is not framed as routing advice. The agent must infer whether to move, trim, or copy a region on its own.

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