Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_automation_mode

Idempotent

Set a track gain, pan, plugin, or send control's native automation mode to off, play, write, touch, or latch to control how Ardour records and applies automation.

Instructions

Set native off/play/write/touch/latch mode.

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

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.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that—it does not explain that the operation targets a specific track/control, what happens to existing automation data when switching to 'write' or 'latch', or the existence of a dry-run/preview path.

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

Conciseness2/5

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

The single sentence is short and front-loaded, but its brevity is under-specification rather than economy—it spends its only words restating the mode enum from the schema while omitting everything else the caller 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?

An output schema exists, so return values need not be explained, but the tool mutates automation state on a track/control with optional dry-run and confirmation flags. Given that complexity and the 0% schema description coverage, the description is far too thin for an agent to call it safely and correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 eight nested fields including dry_run, confirm_delete, expected_revision, processor_id, and parameter_index, none of which the description mentions. The only field-level meaning the description conveys is the mode enum, which is already fully enumerated in the schema, so it adds no meaning beyond structured data.

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 verb 'Set' and the enumeration of the five mode values are concrete, but the resource is only implied ('native ... mode') and the name is needed to know that this is automation mode. It does not differentiate itself from siblings such as clear_automation or create_automation_points, which an agent could plausibly confuse it with.

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 guidance, no mention of prerequisites (e.g. that a control/track must exist or be armed), and no reference to alternatives such as clear_automation. The agent must infer all selection logic 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