Skip to main content
Glama

Boost.Audio

by audio.boost.mcp

Boost Audio - Studio Builder

boost_audio_studio_builder

Open Soundra-style studio wizard inside this conversation. Asks the user 4 short questions (purpose, genre, budget, room size) and builds 3 studio proposals (budget / optimal / premium) with hardware per slot (microphone, audio interface, monitors, headphones, MIDI controller, DAW) and direct purchase links to supersound.pl with UTM tracking. Use when the user asks to recommend studio gear, plan a home studio for X PLN/EUR, swap a device, or compare price tiers. IMPORTANT: ALWAYS pass locale (pl/en/de) inferred from the user's chat language so prices are localized (PL=PLN, EN/DE=EUR) and product names + supersound.pl URLs are returned in the right language.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSetup name for `_action='save'`. Defaults to 'Setup z MCP — {timestamp}'.
slotNoOptional slot id for `_action='search'` (e.g. 'microphone', 'interface'). Goes into `utm_content` for finer attribution.
itemsNoSetup payload for `_action='save'`. Free-form object — typically `{ slots: {...}, accessories: [...], total_price: number }`.
limitNoOptional result limit for `_action='search'` (1-20, default 6).
budgetNoTotal budget in PLN (or EUR for en/de locale). Required for `_action='build'`. Distributed across slots according to `purpose`. Range: 500-50000.
localeNoLocalizes prices (PL=PLN, EN/DE=EUR) and supersound.pl shop URL prefix (/eu/ for EN, /de/ for DE).
searchNoFree-text search for `_action='search'`, e.g. 'Shure SM7B' or 'Focusrite Scarlett'.
_actionNoAction selector. 'build' (default): generate 3 proposals from budget+purpose. 'search': find specific products by category. 'get_mine': list saved setups (OAuth). 'save': persist current setup to user's account (OAuth).
purposeNoPrimary use case. Drives slot allocation: 'vocal'=mic/interface heavy, 'podcast'=mic 35%/interface 20%, 'beat-making'=MIDI 20%/monitors 25%, 'production'=balanced studio, 'general'=balanced.
categoryNoProduct category for `_action='search'`. Aliases internally to WooCommerce category slugs.
max_priceNoOptional max price filter for `_action='search'`.
min_priceNoOptional min price filter for `_action='search'`.
room_sizeNoRoom size hint (informational, used by widget for monitor pair size suggestions).
total_priceNoOptional total price hint for `_action='save'`.
conversation_idNoOptional conversation/session id from the LLM client. Goes into `utm_term` for sales attribution per chat session.

TDQS

A4.3/5.0
Behavior4/5

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

It discloses the interactive flow (asks 4 questions), output shape (3 tiers with hardware per slot), and localization/UTM behavior, all of which are valuable beyond the minimal annotations. It does not detail OAuth/save side effects, but there is no contradiction with the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: main behavior first, then use cases, then a highlighted locale requirement. It is slightly redundant with the schema (hardware slot list, category examples), which prevents a perfect score, but it remains compact and readable.

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?

With 15 parameters and no output schema, the description covers the primary build flow and return structure well (3 proposals, hardware slots, links). It does not elaborate on search/save action outputs, but those are partially documented in the parameter 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 coverage is 100%, so the baseline is 3, but the description adds meaningful semantics: locale must be inferred from chat language, budget is distributed by purpose, and purchase links use UTM tracking. This goes beyond the raw schema and helps the agent invoke actions correctly.

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 opens with a specific verb and resource: 'Open Soundra-style studio wizard' that 'builds 3 studio proposals' with hardware slots and purchase links. It clearly distinguishes this from the sibling audio-processing tools by focusing on studio setup recommendations rather than audio manipulation.

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 gives explicit use cases: 'when the user asks to recommend studio gear, plan a home studio for X PLN/EUR, swap a device, or compare price tiers.' It does not explicitly mention when not to use it or name alternatives, but the use-case list is clear enough for an agent to route correctly.

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