Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

set_plugin_parameters

Idempotent

Validate and set a batch of native plugin parameter values; on failure, roll back supported changes to preserve Ardour session consistency.

Instructions

Validate and set a batch of native parameter values; rollback supported values on failure.

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_plugin_parameters"
  }
}

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

Behavior3/5

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

The annotations already establish that this is a non-read-only but non-destructive, idempotent operation. The description adds useful behavioral context by saying rollback is supported on failure, but it remains vague about partial-batch behavior, what exactly gets rolled back, and how dry_run or confirm_delete affect execution.

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?

The description is a single front-loaded sentence with no wasted wording. However, its brevity contributes to missing guidance rather than being optimally sized for a complex nested mutation tool.

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?

This is a complex nested mutation tool with dry_run, confirm_delete, expected_revision, and an array of parameter values. Although an output schema and annotations exist, the description does not provide enough guidance for an agent to call it safely and correctly in all cases.

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 reported as 0% at the top level, and the description does not explain the request fields dry_run, confirm_delete, expected_revision, track_id, processor_id, or the parameters array structure. It adds only limited meaning with phrases like batch and native parameter values, leaving most parameter semantics to the schema alone.

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?

The description gives a specific verb and resource: validate and set a batch of native parameter values. It clearly distinguishes a write operation from a read operation, though it does not explicitly name the sibling get_plugin_parameters or set_plugin_enabled.

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 guidance on when to use this tool instead of alternatives such as get_plugin_parameters, set_plugin_enabled, or preset tools. The description also omits prerequisites and important conditions like when dry_run or confirm_delete should be used.

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

Deploy Server