soundraw-game-bgm

adaptive_layer_control

Generate isolated stem versions of a BGM track by muting specific layers (backing, bass, drums, melody) to enable real-time adaptive mixing for game audio.

Instructions

Generate multiple versions of a track with different stems muted for adaptive game audio. Creates separate audio files for each layer configuration that can be mixed in real-time based on gameplay.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "share_link": "<share_link>",
      "layers_to_keep": "<layers_to_keep>"
    },
    "name": "adaptive_layer_control"
  }
}

Input Schema

Name	Required	Description
`share_link`	Yes	The share_link URL from a previous generate_bgm result
`layers_to_keep`	Yes	Which layers to generate isolated versions for. Each layer creates a version with other layers muted.
`file_format`	No	Audio format (default: m4a)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 26, 2026

TDQS

A3.9/5.0

Behavior3/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. It discloses that the tool creates separate audio files for real-time mixing, but does not mention output details, potential side effects, or error conditions.

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 two sentences, front-loaded with the core action, and contains no unnecessary words. Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description does not specify how results are returned (e.g., file paths or links) and omits dependencies like requiring a share_link from generate_bgm. Given no output schema, more detail on the output format would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with clear descriptions for each parameter. The description adds value by explaining that each selected layer creates a version with other layers muted, clarifying the enum behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: generating multiple versions of a track with different stems muted for adaptive game audio. It distinguishes from siblings like generate_bgm (initial generation) and get_bgm_variations (retrieving existing variations).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for adaptive game audio but does not explicitly state when to use this tool versus alternatives or when not to use it. It provides context but lacks explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server