Skip to main content
Glama

deecho_audio

Remove echo from audio files by processing them through the MusicGPT MCP Server. Upload an audio URL to clean up recordings and improve sound quality.

Instructions

Remove echo from audio

Input Schema

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

Implementation Reference

  • The handler function that implements the core logic for the 'deecho_audio' tool. It validates input, makes a POST request to the '/deecho' API endpoint, and returns a response message with task status information.
    private async handleDeechoAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/deecho", {
        audio_url: args.audio_url,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio de-echo started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • The input schema definition for the 'deecho_audio' tool, part of the TOOLS array used for tool listing in MCP.
      name: "deecho_audio",
      description: "Remove echo 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:689-690 (registration)
    The switch case in the main tool execution handler that routes calls to 'deecho_audio' to the specific handleDeechoAudio method.
    case "deecho_audio":
      return await this.handleDeechoAudio(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. 'Remove echo from audio' implies a processing operation but doesn't specify whether it's destructive, requires authentication, has rate limits, or returns a result. It mentions a webhook for callback, hinting at asynchronous behavior, but this is insufficient for a mutation tool with zero 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 with zero waste. It's front-loaded and appropriately sized for the tool's function, making it easy to parse without unnecessary elaboration.

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 tool's complexity (audio processing with mutation), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns, error conditions, or behavioral traits like async processing. For a tool with 2 parameters and no structured safety hints, more context is needed to guide 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?

Schema description coverage is 100%, so the schema already documents both parameters ('audio_url' and 'webhook_url'). The description adds no additional meaning beyond what the schema provides, such as audio format requirements or webhook payload details. Baseline 3 is appropriate when the schema handles parameter documentation effectively.

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 echo from audio' clearly states the tool's function with a specific verb ('Remove') and resource ('echo from audio'). It distinguishes from siblings like 'denoise_audio' and 'dereverb_audio' by focusing on echo removal, though it doesn't explicitly contrast them. The purpose is unambiguous but could be more specific about scope.

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 prerequisites, context, or exclusions, such as when echo removal is appropriate compared to denoising or dereverberation. With multiple audio processing siblings, this lack of differentiation leaves usage unclear.

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