Skip to main content
Glama

Transport

audacity_transport
Destructive

Control Audacity playback and recording: play a selected region, pause/resume, stop, or record from the cursor with configured input, and check selection and estimated position status.

Instructions

Play a selected region, pause/resume, stop, or record using Audacity’s configured input. Appending requires an explicit audio track matching the configured recording channels (1 or 2). Record mode respects Audacity’s new-track preference, and recording always starts from a cursor point to avoid batch progress waits. status reports selection and a monotonic estimated position; manual transport changes are not tracked. record returns immediately unless duration is supplied.

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": {
      "action": "<action>"
    },
    "name": "audacity_transport"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
trackNo
actionYes
durationNo
newTrackNo

Output Schema

NameRequiredDescriptionDefault
stateYes
selectionYes
positionSourceYes
positionSecondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare the safety profile (readOnly=false, destructive=true, idempotent=false), and the description adds genuinely new behavior: asynchronous record unless duration is supplied, recording starting from a cursor point to avoid batch waits, channel-matching requirements for appends, and the fact that status is a monotonic estimate that ignores manual transport changes. The notable gap is that destructiveHint=true is never explained – nothing says whether recording overwrites existing audio or how that risk is bounded.

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?

The action list is front-loaded and the four sentences are dense with operative detail rather than filler. Some phrasing is compressed to the point of ambiguity (e.g. 'to avoid batch progress waits'), but nothing is redundant.

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 explained, and the description does well on recording semantics. However, for a destructive, 6-parameter, zero-coverage-schema tool it leaves start/end undefined and never states what recording can destroy or what permissions/state are required, so it is adequate rather than complete.

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

Parameters3/5

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

With 0% schema description coverage across 6 parameters, the description has to carry the burden, and it only partly does. It clarifies action values, the track argument's channel-matching requirement, the duration argument's effect on blocking behavior, and implies newTrack via the new-track preference. start and end are never explained (units, whether they define the played region, how they relate to selection) even though their 0–86400 bounds hint at seconds.

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?

The description names the resource (Audacity transport) and enumerates the concrete actions: play, pause, resume, stop, record, status. That is a specific verb+resource statement an agent can match against a request. It stops short of contrasting itself with siblings such as audacity_edit or audacity_generate, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

There is conditional guidance embedded in the text: appending needs an explicit audio track matching the configured channel count, record mode honors the new-track preference, and record returns immediately unless duration is given. These are useful preconditions, but there is no explicit when-to-use/when-not-to-use framing and no named alternative for editing or generating audio.

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