Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

execute_batch

Execute multiple Ardour session edits as one batch with prevalidation, optional dry-run, and rollback for compensable control changes.

Instructions

Prevalidate compensable control edits and apply with rollback; no general ACID promise.

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": "execute_batch"
  }
}

Input Schema

Name	Required	Description	Default
`request`	Yes

Output Schema

Name	Required	Description	Default
`data`	No
`error`	No
`success`	No
`warnings`	No
`revision_after`	No
`changed_objects`	No
`revision_before`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Beyond the annotations, the description discloses two important behaviors: edits are prevalidated before application and rolled back on failure, and there is explicitly no general ACID guarantee. That non-atomicity caveat is exactly the kind of context annotations cannot express. It stops short of describing partial-failure reporting or the effect of the dry-run/confirmation flags.

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, front-loaded sentence with no filler. Its compactness comes at the cost of readability, since the key noun (batch of commands) is never stated plainly.

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 batch executor with nested command items, a delete-confirmation flag, an optimistic-concurrency revision field, and a 100-operation limit, one sentence is far too thin. An output schema exists, so return values need not be covered, but the mutation semantics and flag behaviors are 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 description coverage is 0%, and the request object carries meaningful fields (dry_run, confirm_delete, expected_revision, operations up to 100 items, per-item command/arguments) that the description never mentions. The phrase "prevalidate" hints at dry-run-like behavior and "control edits" hints at command items, but confirm_delete and expected_revision remain completely unexplained.

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?

The description conveys that this applies a set of edits with prevalidation and rollback, which is more specific than the name alone. However, it never plainly says it executes a batch of arbitrary commands, and jargon like "compensable control edits" leaves the actual resource/operation ambiguous for an agent scanning siblings.

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 statement of when to use this versus the many single-operation siblings (create_track, clear_automation, delete_region, etc.), nor when not to use it. The agent must infer that batching is appropriate from the name alone.

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

Deploy Server