Skip to main content
Glama

master_audio

Apply professional audio mastering to enhance sound quality by processing audio files through the MusicGPT MCP Server, improving clarity and balance.

Instructions

Apply professional audio mastering to improve sound quality

Input Schema

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

Implementation Reference

  • The main handler function for the 'master_audio' tool. It validates input, makes a POST request to the '/audio_mastering' endpoint, and returns a formatted response with task status information.
    private async handleMasterAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/audio_mastering", {
        audio_url: args.audio_url,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio mastering started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • Input schema definition for the 'master_audio' tool, specifying required 'audio_url' and optional 'webhook_url' parameters.
    inputSchema: {
      type: "object" as const,
      properties: {
        audio_url: {
          type: "string",
          description: "URL of the audio file to master",
        },
        webhook_url: {
          type: "string",
          description: "URL for callback upon completion",
        },
      },
      required: ["audio_url"],
    },
  • src/index.ts:405-422 (registration)
    Tool registration object in the TOOLS array, which is returned by the ListTools handler.
    {
      name: "master_audio",
      description: "Apply professional audio mastering to improve sound quality",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to master",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url"],
      },
    },
  • src/index.ts:701-702 (registration)
    Case statement in the main tool dispatcher switch that routes 'master_audio' calls to the handleMasterAudio function.
    case "master_audio":
      return await this.handleMasterAudio(args);
Behavior2/5

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

With no annotations, the description carries full burden but only mentions the action and goal. It lacks details on behavioral traits such as processing time, output format, error handling, or whether it's an async operation (implied by webhook_url but not explained). This is inadequate for a tool that likely involves complex audio processing.

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 unnecessary words. It is front-loaded and appropriately sized for a basic overview, earning full marks 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 mastering, no annotations, no output schema, and 2 parameters, the description is insufficient. It doesn't cover what 'improve sound quality' entails, potential side effects, or return values, leaving significant gaps for an AI agent to use it correctly.

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 fully documents both parameters (audio_url and webhook_url). The description adds no additional meaning beyond the schema, such as audio format constraints or webhook payload details, resulting in the baseline score of 3.

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 action ('Apply professional audio mastering') and the goal ('to improve sound quality'), which is specific and distinguishes it from siblings like 'denoise_audio' or 'cut_audio'. However, it doesn't explicitly mention the resource (audio file) beyond what's implied, slightly reducing specificity.

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 'denoise_audio' or 'remix_audio', nor does it mention prerequisites or exclusions. The description only states what it does, leaving usage context entirely to inference.

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