Skip to main content
Glama

Noise Profile

audacity_noise_profile
Destructive

Captures a specified audio interval as a room-tone noise profile in a fresh Audacity process, then applies Noise Reduction; reuse the profile by repeating the same interval.

Instructions

Capture room tone in a fresh Audacity process, then apply NoiseReduction with params={}. Audacity 3.7.8 uses saved UI settings, ignores effect parameters and cannot reset its profile through scripting. Repeating this exact interval reuses its profile; a different interval requires audacity_fresh with backupTo.

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": {
      "track": "<track>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "audacity_noise_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
trackYestrack index (0-based) or unique track name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that Audacity 3.7.8 uses saved UI settings, ignores effect parameters, and cannot reset its profile through scripting, plus the interval-keyed profile reuse behavior. This is exactly the non-obvious context annotations cannot convey; it stops short of saying what the applied noise reduction does to the audio or what is returned.

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?

Three tight sentences, front-loaded with the action and followed by the quirks that constrain correct use. Every sentence carries distinct information; the dense technical phrasing is justified by the tool's unusual state behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter destructive mutation with no output schema, the description covers the important unknowns: parameters are ignored, settings come from the UI, and profile reset requires a fresh process. Missing only parameter units and any hint of the return/verification result.

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?

Schema coverage is only 33% — track is documented but start and end are bare numbers with no description. The description partially compensates by framing start/end as an 'interval' whose exactness controls profile reuse, but never states units or valid range semantics, so half the parameters remain unexplained.

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?

States a concrete two-step operation: capture room tone in a fresh Audacity process, then apply NoiseReduction with params={}. That is a specific verb+resource, and the 'fresh process' phrasing distinguishes it from the generic audacity_effect sibling, though it does not name a direct alternative.

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

Usage Guidelines4/5

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

Gives real routing guidance: repeating the same interval reuses the existing profile, while a different interval requires audacity_fresh with backupTo. It names the alternative and the condition that selects it, but leaves the base case ('when should I use this at all') implied rather than stated.

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