Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

load_plugin_preset

Loads an existing plugin preset by its exact label, enabling precise preset selection on a specified track and processor.

Instructions

Load an existing plugin preset by exact label.

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

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

B3/5.0

Behavior3/5

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

Annotations already declare the safety profile (destructiveHint=false, readOnlyHint=false, idempotentHint=false), so the bar is lower. The description adds the useful behavioral fact that matching is exact rather than fuzzy, but it does not explain the state change a load performs or why a load request carries confirm_delete and dry_run flags.

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

Conciseness5/5

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

One short sentence with the resource and the key constraint front-loaded and no wasted wording. Brevity here is efficient rather than under-specified at the sentence level.

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 the tool takes a structured request with revision-checking and delete-confirmation fields that a load description should address. Given that complexity, one sentence naming only the label leaves an agent guessing about the rest of the request object.

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 single parameter is a nested Preset object with six fields (label, track_id, processor_id, dry_run, confirm_delete, expected_revision). The description mentions only the label and clarifies nothing about the other fields, so it does not compensate for the coverage gap.

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 names a specific verb and resource ('Load an existing plugin preset') plus a scoping constraint ('by exact label'), which distinguishes it from siblings like list_plugin_presets and add_plugin. It stops short of explicitly contrasting with those siblings, so it is clear but not sibling-differentiated.

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?

'By exact label' implies a precondition (the label must already exist and match precisely), but there is no statement of when to use this versus list_plugin_presets to discover labels or add_plugin to create one. No when-not guidance or alternatives are named.

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

Deploy Server