Skip to main content
Glama
Ardour Ultra MCP
by Elias02345

set_track_solo

Idempotent

Set a track's solo state explicitly to on or off in an Ardour session, using its track ID and optional dry-run or revision checks before applying the change.

Instructions

Set route solo explicitly.

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

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.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is largely covered. The description adds nothing beyond that – notably it never explains why a 'solo' setter accepts dry_run and confirm_delete, or how expected_revision affects concurrent edits.

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

Conciseness2/5

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

Four words with no filler, but the brevity is under-specification rather than conciseness; there is no front-loaded statement of scope, effect, or required inputs. Nothing here would be missed if it were expanded.

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 and annotations cover the safety profile, which lowers the bar. Even so, for a mutation tool with five undocumented request fields, an unexplained 'route' vs 'track' mismatch, and undefined 'explicitly' semantics, the description is too thin to call the definition complete.

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% with a single nested 'request' object containing five undocumented fields (track_id, enabled, dry_run, confirm_delete, expected_revision). The description does not mention any of them, so an agent gets no help on what enabled means for solo, or why deletion-confirmation flags appear on a solo operation.

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?

States a verb ('Set') and a resource ('route solo'), which is enough to know it toggles solo state, but the resource is called 'route' here and 'track' in the tool name and in siblings like set_track_mute/set_track_gain. The word 'explicitly' is unexplained and leaves the reader guessing how this differs from a toggle.

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?

No when-to-use guidance, no preconditions, and no named alternative. 'Explicitly' weakly hints at an explicit-boolean counterpart to some implied toggle, but no such tool is named and no condition for choosing one is given.

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