Skip to main content
Glama
DeveloperZo

MCP Audio Tweaker

by DeveloperZo

apply_preset

Apply predefined audio processing presets to optimize files for specific use cases like game audio, voice processing, or music mastering by specifying input/output paths and preset name.

Instructions

Apply predefined audio processing preset optimized for specific use cases

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputFileYesPath to input audio file
outputFileYesPath for output file
presetYesPreset name to apply
overwriteNoWhether to overwrite existing output files

Implementation Reference

  • Handler for apply_preset tool: parses input using ApplyPresetInputSchema, retrieves preset via getPreset, processes audio file using audioProcessor.processAudioFile, and returns result augmented with preset information.
    case 'apply_preset': {
      const input = ApplyPresetInputSchema.parse(args);
      const preset = getPreset(input.preset);
      
      const result = await audioProcessor.processAudioFile(
        input.inputFile,
        input.outputFile,
        preset.operations,
        (args as any).overwrite || false
      );
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({
              ...result,
              presetUsed: preset.name,
              presetDescription: preset.description
            }, null, 2)
          }
        ]
      };
    }
  • Zod schema for validating apply_preset tool inputs: inputFile (audio path), outputFile, preset name.
    export const ApplyPresetInputSchema = z.object({
      inputFile: FilePathSchema,
      outputFile: z.string().min(1),
      preset: PresetNameSchema
    });
  • Tool registration object defining name 'apply_preset', description, and detailed inputSchema for MCP tool listing and validation.
    export const applyPresetTool: Tool = {
      name: 'apply_preset',
      description: 'Apply predefined audio processing preset optimized for specific use cases',
      inputSchema: {
        type: 'object',
        properties: {
          inputFile: {
            type: 'string',
            description: 'Path to input audio file'
          },
          outputFile: {
            type: 'string',
            description: 'Path for output file'
          },
          preset: {
            type: 'string',
            description: 'Preset name to apply',
            enum: [
              'game-audio-mobile',
              'game-audio-desktop',
              'game-audio-console',
              'elevenLabs-optimize',
              'voice-processing',
              'music-mastering',
              'sfx-optimization',
              'deep-mechanical',
              'bright-crystalline',
              'variation-pack',
              'layered-impact',
              'space-ambient',
              'punchy-game-sfx'
            ]
          },
          overwrite: {
            type: 'boolean',
            description: 'Whether to overwrite existing output files',
            default: false
          }
        },
        required: ['inputFile', 'outputFile', 'preset']
      }
    };
  • Includes applyPresetTool in the exported tools array for MCP server registration via registerTools.
    applyPresetTool,
Behavior2/5

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

With no annotations provided, the description carries full burden but lacks critical behavioral details. It doesn't disclose whether this is a read-only or destructive operation, what happens if the output file exists (beyond the 'overwrite' parameter), performance characteristics, or error conditions. The description adds minimal context beyond the basic action.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for the tool's complexity and gets straight to the point with zero waste.

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

Completeness2/5

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

For a tool with 4 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what the tool returns, what happens during processing, error handling, or performance expectations. The mention of 'optimized for specific use cases' is too vague to be helpful without elaboration.

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 100% schema description coverage, the schema already documents all 4 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain what the presets do, provide examples, or clarify relationships between parameters. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb 'apply' and the resource 'predefined audio processing preset', specifying it's optimized for specific use cases. It distinguishes from siblings like 'process_audio_file' by focusing on preset application rather than general processing, though it doesn't explicitly name alternatives.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'process_audio_file' or 'advanced_process'. The description mentions 'optimized for specific use cases' but doesn't specify what those cases are or when to choose this over other tools.

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/DeveloperZo/mcp-audio-tweaker'

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