Skip to main content
Glama

engine_master

Apply a complete mastering chain to the master bus for any of 35 music styles. Auto-detects FabFilter or falls back to REAPER stock plugins, targeting style-specific loudness and true-peak ceiling.

Instructions

Apply a professional mastering chain to the master bus for the given style.

Chain applied (in order): HP 25Hz → bus glue comp → tonal shelf EQ → stereo width → brick-wall limiter. Targets per-style LUFS and true-peak ceiling.

Auto-detects FabFilter Pro-L 2 / Pro-C 2 / Pro-Q 3; falls back to REAPER stock (ReaLimit / ReaComp / ReaEQ).

Supported styles: melodic_dubstep, big_room, future_bass, future_house, deep_house, tech_house, progressive_house, dubstep, trap, drum_and_bass, trance, modern_pop, dance_pop, indie_pop, rnb_pop, alt_rock, classic_rock, pop_rock, hard_rock, punk, post_rock, synthwave, lofi, ambient, hiphop, swing_jazz, jazz_fusion, latin_jazz, classical_chamber, cinematic_trailer, ambient_orchestral, classic_funk, motown_soul, neo_soul, disco_funk (35 total). Any other name falls through to the legacy per-instrument orchestral master chain.

Args: style: Style name from the catalog (required). clean: Remove previously added master FX before applying (default True).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cleanNo
styleYes
Behavior4/5

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

With no annotations, the description thoroughly explains the mastering chain, plugin detection and fallback, per-style targets, and the fallback behavior for unknown styles. It also notes the clean parameter removes existing FX. However, it does not describe post-conditions or potential side effects beyond applying the chain.

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-organized and front-loaded with the purpose, then details. The long list of styles could be condensed, but it adds necessary context. Overall, each sentence serves a purpose.

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

Completeness5/5

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

Given the complexity of a mastering tool with auto-detection, fallback, and 35 styles, the description covers all essential aspects: chain order, plugin behavior, per-style targets, fallback, and parameter semantics. It is complete for an agent to select and invoke correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates by defining style as a required catalog name and listing all 35 supported styles, and explaining that clean removes previously added master FX. This provides meaning beyond the schema's type and default.

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 applies a professional mastering chain to the master bus, detailing the chain order, plugins, and supported styles. It distinguishes itself from sibling tools like engine_mix or engine_fix_mix by focusing solely on mastering.

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 explicit guidance on when to use this tool versus alternatives like engine_mix or engine_fix_mix. The description does not mention prerequisites, scenarios, or exclusion criteria.

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/xDarkzx/Reaper-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server