Skip to main content
Glama

audacity_health_check

Check Audacity's availability and identify reasons for connection failures. Use this diagnostic tool when commands time out or return empty responses.

Instructions

Check whether Audacity is reachable, and why not if it isn't.

Run this first when anything fails in a way that might not be about the command you sent: no response, an empty response, a timeout, or an export that came out wrong. Reports both script pipes separately, how old they are, whether a round trip actually answers, which copy of the client is installed, and the default project sample rate — plus what to do about whatever it finds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so the description carries full burden. It transparently explains what it reports (script pipes, age, round trip, client version, sample rate) and that it offers solutions. No behavioral surprises; no contradictions.

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?

Description is concise (two sentences) and front-loaded: first sentence states core purpose, second expands on specifics. Every sentence adds value with no redundancy.

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

Completeness5/5

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

No output schema exists, but the description adequately explains what the tool returns (diagnostic info and recommended actions). Given the tool's simplicity and lack of parameters, the description is complete.

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?

Tool has zero parameters (schema is empty, 100% coverage). Description adds no parameter info, which is acceptable. Baseline for 0 params is 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the purpose: check reachability and diagnose failures. It lists specific checks (script pipes, age, round trip, client copy, sample rate) and actionable advice, distinguishing it from sibling tools which are editing/analysis/transport commands.

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

Usage Guidelines5/5

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

Explicitly instructs to run this first when things fail (no response, empty response, timeout, bad export), providing clear when-to-use context. It doesn't name alternatives but the diagnostic role is evident.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/robworks-code/audacity-mcp-max'

If you have feedback or need assistance with the MCP directory API, please join our Discord server