Ardour Ultra MCP

Overview Schema Source Related Servers Discussions Admin

delete_track

Destructive

Permanently removes a non-singleton track from an Ardour session, requiring explicit confirmation since the deletion cannot be undone natively.

Instructions

Delete a non-singleton route; explicit confirm_delete required; not natively undoable.

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

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

A3.6/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds genuinely new behavioral context: the operation is 'not natively undoable', which meaningfully raises the caution level beyond the annotation set. It still omits what happens to references/routing after deletion, so it is not fully transparent.

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 compact sentence, semicolon-delimited, with the destructive scope and the safety prerequisite front-loaded. Every clause carries information; no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 not be described. However, for a destructive, non-idempotent mutation with 0% parameter documentation, the description should explain dry_run semantics and expected_revision conflict behavior; it does not.

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 request object carries four sub-properties (track_id, dry_run, confirm_delete, expected_revision). The description only touches confirm_delete, leaving dry_run and especially expected_revision (a concurrency/optimistic-locking field) completely unexplained.

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?

States a specific verb and resource ('Delete a non-singleton route') and adds a scope constraint that distinguishes it from sibling deletes like delete_group or delete_region. The only weakness is terminology drift: the tool is delete_track but the description says 'route', which could momentarily confuse an agent.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear applicability condition ('non-singleton') and a hard prerequisite ('explicit confirm_delete required'), which is enough for an agent to know when this call will succeed. It does not name an alternative for singleton deletion, so the guidance stops short of full routing.

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

Deploy Server