Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

rename_track

Renames a track by its stable ID in an Ardour session, enabling agents to update track names while preserving routing and identity.

Instructions

Rename a stable-ID route.

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

Input Schema

NameRequiredDescriptionDefault
requestYes

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
successNo
warningsNo
revision_afterNo
changed_objectsNo
revision_beforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, and closed-world, so the safety profile is partly covered. The description adds nothing beyond that, and notably the schema exposes a confirm_delete flag and an expected_revision concurrency token that hint at destructive/optimistic-locking behavior the description never explains. No mention of dry_run semantics or what a rename does to references elsewhere.

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

Conciseness3/5

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

The single sentence is front-loaded and contains no filler, so there is nothing to cut. The problem is under-specification rather than verbosity. Brevity here costs more than it saves.

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 not be explained, which is the one thing counting in its favor. But this is a mutating tool with a dry-run mode, a confirm_delete flag, and a revision-precondition parameter, all of which need behavioral explanation the description does not provide. Completeness is well short of what the tool's complexity demands.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five nested properties (track_id, name, dry_run, confirm_delete, expected_revision), so the description must compensate and instead adds nothing. The meanings of confirm_delete and expected_revision are non-obvious and completely undocumented in prose. The name pattern constraint is also only in the schema, not translated into guidance.

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?

The description pairs a specific verb ("Rename") with a resource ("stable-ID route"), so the core action is inferable. However, it calls the resource a "route" while the tool name and schema refer to a track, which creates ambiguity about what object is being mutated. It also does nothing to distinguish this from sibling track-mutation tools.

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 at all on when to use this versus alternatives such as create_track, get_track, or execute_batch. No prerequisites, no mention of whether the track must exist or be a specific type are given. The one-sentence description leaves all routing decisions to the agent.

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