Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_group_properties

Idempotent

Configure Ardour track group link booleans (gain, mute, solo, select) by group ID and return before/after state; changes are not wrapped in grouped undo.

Instructions

Set explicit group linkage booleans; returns before/after state; no grouped 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": "set_group_properties"
  }
}

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

Behavior3/5

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

The description adds real context beyond the annotations: it returns before/after state and that there is "no grouped undo" — valuable for a mutation. But it stays silent on the dry_run vs. confirm_delete interaction and expected_revision conflict handling, which are the most consequential behaviors for a write tool with destructiveHint=false.

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?

Three semicolon-separated clauses, front-loaded with the action, with no filler. It is efficient, though the compression is extreme enough that key operational details were dropped rather than merely shortened.

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 no explanation, but for a write tool with ten optional booleans, a dry-run mode, a destructive-confirmation flag, and a revision guard, the description leaves too much unspecified. It should at minimum explain what happens when properties are omitted and how confirmation/revision checks behave.

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 nested GroupProperties object carries ten undescribed booleans plus dry_run, confirm_delete, and expected_revision. The description explains none of them, so it fails to compensate for the coverage gap and leaves semantics like revision concurrency entirely to inference.

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?

"Set explicit group linkage booleans" names a verb and a resource, and the word "group" distinguishes it from per-track/per-plugin siblings. However, "linkage booleans" is jargon that does not map obviously to the schema fields (gain, mute, solo, color, monitoring, etc.), so an agent still has to open the schema to know what is being set.

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 per-object setters like set_track_mute or set_monitoring, nor when not to use it. Nothing indicates that the parameters include a dry_run gate, a confirm_delete flag, or a revision check, so the agent gets no routing or precondition guidance.

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

Deploy Server