Skip to main content
Glama

Boost.Audio

by audio.boost.mcp

Boost Audio - Audio to MIDI

boost_audio_to_midi

Convert a melody or drum track from audio to a downloadable MIDI file. Use midi_mode='melody' (default) for pitched instruments/vocals, 'drums' for drum transcription.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlNoOptional public URL to an audio/video file. If omitted, the user uploads the file in the rendered widget.
file_nameNoOriginal file name. Required when audio_base64 is provided.
file_typeNoOriginal mime type. Required when audio_base64 is provided.
midi_modeNo'melody' for pitched instruments/vocals (default), 'drums' for drum transcription.melody
stem_hintNoInstrument type hint for melody mode — helps the transcription engine. Ignored when midi_mode is 'drums'.other
file_tokenNoToken for a pre-uploaded large file (>22 MB). Obtained from POST /widget-api/upload-raw. Used instead of audio_base64 for large files.
audio_base64NoOptional base64-encoded audio file payload. Used by the widget when the host iframe blocks CORS fetches.

TDQS

A4/5.0
Behavior3/5

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

Annotations already disclose readOnlyHint=false and destructiveHint=false, and the description adds that a downloadable MIDI file is produced. However, it does not explain processing time, limitations, or upload requirements, which are left to the schema. This is adequate but not rich.

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 long, front-loaded with the primary purpose, and has no redundant filler. Every sentence adds value: the first defines the core operation, the second explains parameter usage.

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?

Given the rich input schema (100% parameter descriptions) and the presence of annotations, the description is fairly complete. It mentions the output type (downloadable MIDI file) and the key mode distinction. It lacks details about return format or edge cases, but the schema covers parameter specifics.

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 all parameters already have descriptions. The tool description merely reiterates the midi_mode parameter without adding new semantic meaning beyond what the schema provides. Thus the baseline of 3 applies.

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 converts audio to a downloadable MIDI file, specifying melody or drum tracks. This distinguishes it from sibling tools like audio converter or stem splitter. The verb 'convert' and resource (audio to MIDI) are explicit.

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?

The description provides specific usage guidance for midi_mode, explaining when to use 'melody' versus 'drums'. However, it does not explicitly mention when to choose this tool over alternatives or include exclusions, so it stops short of a full 5.

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

All Boost.Audio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool targets a unique audio processing task (e.g., BPM/key detection, format conversion, stem splitting) with no functional overlap, ensuring agents can easily distinguish between them.

Naming Consistency5/5

All tool names follow a strict `boost_audio_verb_noun` pattern in snake_case, providing a predictable and clean naming convention across the entire set.

Tool Count5/5

With exactly 8 tools, the server is well-scoped for an audio processing domain—comprehensive enough to cover key tasks without being overwhelming or sparse.

Completeness4/5

The tools cover essential audio operations (conversion, extraction, generation, splitting, trimming, etc.), but a merging or concatenation tool is missing, leaving a minor gap.

Resources