Ardour Ultra MCP

by Elias02345

Overview Schema Source Related Servers Discussions Admin

Python

Local

get_track

Read-onlyIdempotent

Inspect an Ardour route by its persistent ID to retrieve track details before editing or validating session changes.

Instructions

Inspect a route by persistent Ardour ID.

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": "get_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

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description's only addition is that the ID is persistent, implying stable lookups across sessions. It says nothing about error behavior when the ID is unknown or what relationship a route has to a track.

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. Its brevity is clean, though it borders on under-specification rather than tight writing.

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. For a one-parameter lookup, the definition is close to sufficient, but with 0% schema coverage on a nested request object containing three obscure fields, the agent is left guessing about confirm_delete and expected_revision.

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 must carry the parameter load, and it only maps "persistent Ardour ID" to track_id. The nested request object also holds dry_run, confirm_delete, and expected_revision, which go entirely unexplained. In particular, confirm_delete on a read-only inspection tool is confusing and invites an unwarranted write assumption.

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?

"Inspect a route by persistent Ardour ID" gives a specific verb (inspect), resource (route), and lookup key (persistent Ardour ID). It does not differentiate from siblings such as get_region or get_automation, and it uses "route" where the tool name says "track," which is a small terminology mismatch an agent must reconcile.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusion of the many other get_* tools. The agent must infer from the name and the phrase "persistent Ardour ID" alone that this is the point-lookup counterpart to any list operation.

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

Deploy Server