Ardour Ultra MCP

by Elias02345

Overview Schema Source Related Servers Discussions Admin

Python

Local

redo

Reapply the last undone edit in an Ardour session by triggering the editor's native forward-history action once.

Instructions

Invoke Editor native redo once.

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

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?

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The word 'once' usefully reinforces that each call advances the redo stack by exactly one step, matching non-idempotence, but nothing is said about behavior when the redo history is empty or about any error/return semantics.

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?

One short, front-loaded sentence with no filler. It is appropriately sized for a trivial single-action tool, though it spends its few words on 'native' rather than on the parameters that need explaining.

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?

The tool is simple and an output schema exists, but the wrapped request object exposes dry_run, confirm_delete and expected_revision with zero documentation anywhere, and no failure mode is described. For a state-mutating editor action this leaves meaningful gaps.

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 'request' object actually carries dry_run, confirm_delete and expected_revision flags that the description never mentions. An agent cannot learn from the text whether a dry run or revision guard applies to a redo, so the description 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 (redo) and resource (the Editor's native redo stack), and the word 'once' scopes it to a single step. It is clear what the tool does, though 'Editor native' is somewhat jargon-dependent and no sibling is named for contrast.

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 beyond the implicit 'when you want to redo'. Nothing states prerequisites (e.g. there must be something in the redo history) or when to prefer an alternative such as editing state directly; the single sentence is purely descriptive.

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

Deploy Server