Gizmos Audacity MCP

Overview Schema Source Related Servers Discussions Admin

Import

audacity_import

Import an audio or video file’s sound as a new Audacity track, optionally naming it and placing it at a specified start time.

Instructions

Import an audio (or video, for its sound) file as a new track, name it and place it at start seconds.

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": {
      "file": "<file>"
    },
    "name": "audacity_import"
  }
}

Input Schema

Name	Required	Description	Default
`file`	Yes
`name`	No
`start`	No

Output Schema

Name	Required	Description	Default
`name`	Yes
`track`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds genuine context beyond that — the result is a NEW track rather than a replacement, and video input is accepted for its sound. It omits what happens on failure (missing/unsupported file), whether repeated calls stack duplicate tracks, and any partial-import behavior.

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

Conciseness5/5

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

One sentence, front-loaded with the action and resource, with the essential qualifiers (video-for-sound, new track, placement) packed in and 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 no explanation, and the tool is structurally simple (3 params, no nesting). Still missing for a file-swallowing importer: supported formats, path resolution rules, and failure semantics — gaps an agent would hit on first call.

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

Parameters4/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 semantics, and it does: file may be audio or video (audio extracted), name sets the track name, start is the placement time in seconds. It does not clarify whether file is an absolute path or workspace-relative, nor what name defaults to, which keeps it below 5.

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?

Specific verb+resource: 'Import an audio (or video, for its sound) file as a new track'. It is clearly distinct from generate/launch/export siblings by acting on an existing file, though it does not explicitly name a sibling to differentiate against.

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?

Usage is only implied: import covers files that already exist on disk, versus audacity_generate for synthesized audio. There is no explicit when-to-use/when-not statement, no mention of required preconditions (e.g., a project being open), and no guidance on format or path constraints.

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

Deploy Server