Skip to main content
Glama
Sign In
Gizmos Audacity MCP

Gizmos Audacity MCP

by gizmos-quest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Targets

audacity_targets
Read-onlyIdempotent

Lists numeric house reference targets for podcast, video, broadcast, audiobook, and premaster audio so you can compare measured levels against suitable targets.

Instructions

List numeric house reference targets for podcast, video, broadcast, audiobook and premaster; use these with measurement targets. These references are not publishing certification. Recording noise floor requires isolated room tone.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audacity_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteYes
presetsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered and the bar is lower. The description adds genuine scope context beyond annotations — that these are house references and not publishing certification, plus a caveat that noise-floor figures assume isolated room tone. The room-tone sentence is only loosely connected to a targets-listing call, which keeps this at a 3.

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 core purpose is front-loaded in the first clause and the caveats follow compactly. The final sentence about isolated room tone is a slight non-sequitur in a list tool and could be trimmed, but overall there is no filler or repetition.

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?

An output schema exists, so the description need not explain return values, and with no inputs the surface area is small. It covers what the data is and what it is not (not certification), which is enough for an agent to call it correctly; only the relationship to the measurement siblings remains implicit.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly frames the call as an unfiltered full listing of the reference set, with no argument-level behavior to document.

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 gives a specific verb and resource ("List numeric house reference targets") and enumerates the content categories: podcast, video, broadcast, audiobook and premaster. An agent can tell this is a static reference table lookup rather than a measurement, but it never names the sibling it pairs with (audacity_loudness_target / audacity_measure), so sibling differentiation is only implied.

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?

"use these with measurement targets" implies the workflow (fetch targets, then compare against measurements) and the caveat about publishing certification sets a scope boundary. However, there is no explicit when-to-use versus audacity_loudness_target or audacity_measure, and no stated prerequisite ordering, leaving the agent to infer the sequencing.

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

Deploy Server

Other Tools