Ardour Ultra MCP

by Elias02345

Overview Schema Source Related Servers Discussions Admin

Python

Local

render_range

Export a master audio range using an existing Ardour export preset into a new isolated output directory.

Instructions

Export master range using actual Ardour preset into a new isolated directory.

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

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

Behavior2/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent write, so the safety framing is partly covered, and 'new isolated directory' usefully hints at output isolation. But the description never mentions the meaningful behavioral switches in the request object: dry_run for previewing, confirm_delete for overwriting an existing directory, or expected_revision for optimistic concurrency. Those are exactly the traits an agent needs beyond the annotations.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity reflects under-specification rather than disciplined editing.

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 mutating export tool wrapped around a fairly complex request object with concurrency and deletion-confirmation semantics. An output schema exists, so return values needn't be described, but the description leaves far too much of the invocation contract implicit for a tool of this complexity.

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%, so the description bears the burden of explaining parameters, yet it only alludes to the preset and the output directory. The start/end position variants, the empty-string preset default meaning SimpleExport, dry_run, confirm_delete, and expected_revision all go unexplained in the prose.

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?

Names a specific verb (Export) and resource (master range), plus the mechanism (Ardour preset) and destination (new isolated directory). However 'master range' is vague about what is actually rendered (session master output over a time range?) and it gives no indication of how it differs from the sibling render_and_analyze.

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 choose this over render_and_analyze or any other render path, no prerequisites, and no exclusions. The agent must infer usage entirely from the name and schema.

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

Deploy Server