Skip to main content
Glama

dereverb_audio

Remove reverb from audio files to enhance clarity and quality. Process audio via URL input for cleaner sound output.

Instructions

Remove reverb from audio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesURL of the audio file to process
webhook_urlNoURL for callback upon completion

Implementation Reference

  • The main handler function for the 'dereverb_audio' tool. Validates the input audio_url, makes a POST request to the MusicGPT API '/dereverb' endpoint, and returns a response with task details and instructions for checking status.
    private async handleDereverbAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/dereverb", {
        audio_url: args.audio_url,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio de-reverb started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • Tool registration in the TOOLS array including name, description, and input schema definition for validation. Used by the MCP ListTools handler.
    {
      name: "dereverb_audio",
      description: "Remove reverb from audio",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to process",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url"],
      },
    },
  • src/index.ts:691-692 (registration)
    Dispatch case in the CallToolRequestHandler switch statement that routes calls to the 'dereverb_audio' handler.
    case "dereverb_audio":
      return await this.handleDereverbAudio(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Remove reverb from audio' implies a processing action, it doesn't reveal whether this is a synchronous or asynchronous operation (the webhook_url parameter suggests async), what permissions or authentication might be required, potential rate limits, or what the output looks like. This is a significant gap for a tool with no annotation coverage.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the core purpose, making it easy to scan and understand immediately, which is ideal for efficient tool selection.

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 the complexity of audio processing and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'remove reverb' entails operationally, what formats are supported, whether the processing is destructive, or what the result looks like. For a tool with no structured output information, this leaves too many unknowns for effective use.

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 description adds no parameter-specific information beyond what's already in the input schema, which has 100% coverage with clear descriptions for both 'audio_url' and 'webhook_url'. Since the schema fully documents the parameters, the baseline score of 3 is appropriate—the description doesn't compensate but doesn't need to given the comprehensive schema.

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 'Remove reverb from audio' clearly states the tool's function with a specific verb ('Remove') and resource ('reverb from audio'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'deecho_audio' or 'denoise_audio' that might handle similar audio processing tasks, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. With sibling tools like 'deecho_audio' and 'denoise_audio' available, there's no indication of how 'dereverb_audio' differs in scope or application, leaving users to guess based on tool names alone.

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/pasie15/mcp-server-musicgpt'

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