Skip to main content
Glama
DeveloperZo

MCP Audio Tweaker

by DeveloperZo

list_presets

Browse available audio processing presets for game, voice, music, and effects categories to optimize audio files with FFmpeg configurations.

Instructions

List all available audio processing presets with their descriptions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter presets by category

Implementation Reference

  • Handler logic for 'list_presets' tool within the main tool dispatcher. Imports utilities from presets.js and returns JSON list of presets, filtered by category if provided.
    case 'list_presets': {
      const { listPresets, getPresetsByCategory } = await import('../utils/presets.js');
      const category = (args as any)?.category;
      
      const presets = category ? getPresetsByCategory(category) : listPresets();
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(presets, null, 2)
          }
        ]
      };
    }
  • Tool definition including name, description, and input schema for optional category filter.
    export const listPresetsTool: Tool = {
      name: 'list_presets',
      description: 'List all available audio processing presets with their descriptions',
      inputSchema: {
        type: 'object',
        properties: {
          category: {
            type: 'string',
            description: 'Filter presets by category',
            enum: ['game', 'voice', 'music', 'effects'],
            optional: true
          }
        }
      }
    };
  • Registration of listPresetsTool in the exported tools array used for listing available tools.
    listPresetsTool,
  • Core helper function that returns all preset definitions from the PRESETS object.
    export function listPresets(): PresetDefinition[] {
      return Object.values(PRESETS);
    }
  • Helper function to filter presets by category, used when category is provided in tool input.
    export function getPresetsByCategory(category: 'game' | 'voice' | 'music' | 'effects'): PresetDefinition[] {
      const gamePresets = ['game-audio-mobile', 'game-audio-desktop', 'game-audio-console'];
      const voicePresets = ['elevenLabs-optimize', 'voice-processing'];
      const musicPresets = ['music-mastering'];
      const effectsPresets = ['sfx-optimization'];
      
      let presetNames: PresetName[] = [];
      
      switch (category) {
        case 'game':
          presetNames = gamePresets as PresetName[];
          break;
        case 'voice':
          presetNames = voicePresets as PresetName[];
          break;
        case 'music':
          presetNames = musicPresets as PresetName[];
          break;
        case 'effects':
          presetNames = effectsPresets as PresetName[];
          break;
      }
      
      return presetNames.map(name => PRESETS[name]);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it lists presets, implying a read-only operation, but doesn't cover aspects like whether it requires authentication, rate limits, pagination, or error handling. This leaves significant gaps for a tool with no annotation support.

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 directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded, making it easy to understand at a glance.

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?

Given no annotations and no output schema, the description is incomplete. It doesn't explain what the output looks like (e.g., list format, included fields like preset names and descriptions), behavioral traits, or usage context. For a tool with rich sibling tools and no structured support, this is inadequate.

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?

The input schema has 100% description coverage, documenting the optional 'category' parameter with its enum values. The description adds no additional parameter semantics beyond what the schema provides, such as default behavior when no category is specified. Baseline 3 is appropriate as the 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 ('List') and resource ('audio processing presets') with their descriptions, making the purpose specific and understandable. However, it doesn't explicitly differentiate this tool from potential siblings like 'apply_preset' or 'process_audio_file' beyond the listing action.

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. It doesn't mention prerequisites, such as needing presets to exist, or compare it to sibling tools like 'apply_preset' for applying presets or 'process_audio_file' for processing with presets.

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