Boost.Audio

Boost Audio - Stem Splitter

boost_audio_stem_splitter

Split a song into separate stems with Boost Audio AI: vocals, drums, bass and other (4-stem mode). Ultimate plan unlocks a 6-stem mode with separate guitar and piano. Use this when the user wants individual instrument stems.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "boost_audio_stem_splitter"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No	Stem separation mode. 6-stem requires Ultimate plan.	4-stem
`audio_url`	No	Optional public URL to an audio/video file. If omitted, the user uploads the file in the rendered widget.
`file_name`	No	Original file name. Required when audio_base64 is provided.
`file_type`	No	Original mime type. Required when audio_base64 is provided.
`file_token`	No	Token for a pre-uploaded large file (>22 MB). Obtained from POST /widget-api/upload-raw. Used instead of audio_base64 for large files.
`audio_base64`	No	Optional base64-encoded audio file payload. Used by the widget when the host iframe blocks CORS fetches.

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With annotations already indicating readOnlyHint=false and destructiveHint=false, the description adds valuable context about plan requirements ('Ultimate plan unlocks a 6-stem mode') and the difference in output stems. No contradiction with annotations. It does not detail all side effects (e.g., upload limits, processing time), but adds sufficient behavior beyond annotations.

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?

Two sentences, front-loaded with the core action and outputs. Every clause is relevant, including the plan note and usage hint. No redundant filler.

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

Completeness4/5

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

No output schema exists, but the description implies the result (separate stems) by stating the purpose. It covers the main workflow and mentions the plan limitation. Lacks explicit details on how results are delivered, but is adequate for a moderately complex tool with rich input schema descriptions.

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 description coverage is 100%, so baseline is 3. The description enriches the 'mode' parameter by explaining what 4-stem vs 6-stem yields ('separate guitar and piano'), which is not fully captured in the schema's enum description. This adds practical meaning.

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 uses a specific verb 'Split' and clearly identifies the resource ('a song into separate stems') with explicit outputs (vocals, drums, bass, other). It also distinguishes from sibling tools by stating 'Use this when the user wants individual instrument stems.'

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

Usage Guidelines4/5

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

Provides clear context for when to use the tool: 'Use this when the user wants individual instrument stems.' It does not explicitly mention alternatives or exclusions, but the context is specific and actionable.

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

All Boost.Audio tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?