Skip to main content
Glama

denoise_audio

Remove background noise from audio files to improve clarity and quality. Process audio by providing a URL, with optional webhook notification upon completion.

Instructions

Remove background noise from audio

Input Schema

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

Implementation Reference

  • The main handler function for the 'denoise_audio' tool. It validates the input, makes a POST request to the MusicGPT API '/denoise' endpoint with audio_url and optional webhook_url, and returns the response details including task_id for status checking.
    private async handleDenoiseAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/denoise", {
        audio_url: args.audio_url,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio denoising started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • Tool definition in the TOOLS array, providing the name, description, and input schema (requiring audio_url, optional webhook_url). This is used for tool listing and validation.
    {
      name: "denoise_audio",
      description: "Remove background noise from audio",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to denoise",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url"],
      },
    },
  • src/index.ts:687-688 (registration)
    In the main CallToolRequestSchema handler's switch statement, routes 'denoise_audio' tool calls to the specific handleDenoiseAudio method.
    case "denoise_audio":
      return await this.handleDenoiseAudio(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 background noise' implies a transformation, it doesn't disclose critical traits like whether this is a destructive operation, requires specific permissions, has rate limits, or what the output entails (e.g., format, quality changes). This is inadequate 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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly, earning a perfect score for conciseness.

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, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects, output format, error handling, or integration with sibling tools. This leaves significant gaps for an agent to understand the tool's full context and usage.

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?

Schema description coverage is 100%, with both parameters ('audio_url', 'webhook_url') fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as explaining parameter interactions or constraints. This meets the baseline score of 3 when 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 'Remove background noise from audio' clearly states the tool's function with a specific verb ('Remove') and resource ('background noise from audio'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'deecho_audio' or 'dereverb_audio' which might handle similar audio processing tasks, preventing 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. It doesn't mention any prerequisites, context for use, or exclusions, and with multiple sibling tools for audio processing (e.g., 'deecho_audio', 'dereverb_audio'), the lack of differentiation leaves the agent without clear usage instructions.

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