Skip to main content
Glama

equalizer_preset

Apply a named equalizer preset and switch the equalizer on, so you can lift dialogue from loud mixes or tame explosions while keeping voices audible.

Instructions

Apply a named equaliser curve and switch the equaliser on. Use equalizer_presets to see what exists and what each is for. 'speech' lifts dialogue out of a loud mix and 'night' tames explosions while keeping voices — those two answer most requests about not being able to hear what people are saying.

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": {
      "name": "<name>"
    },
    "name": "equalizer_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPreset name, e.g. speech, night, bass, treble, headphones, flat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the non-obvious side effect that the equaliser is switched on, not just set. It does not say what happens with an unknown preset name, whether the setting persists across sessions, or what the call returns, which are notable gaps for a state-changing tool with zero annotation coverage.

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?

Three short sentences, front-loaded with the action and side effect, then the discovery alternative, then the payoff for the two most likely intents. The em-dash explanation is longer than strictly needed but directly supports preset selection, so it earns its place.

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?

For a one-parameter, no-output-schema, unannotated tool this covers purpose, alternative discovery route, and value selection well. Only failure behavior (invalid preset name) and persistence are left unaddressed, which is a minor residual gap.

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% and the schema already lists candidate names, so the baseline is 3. The description goes beyond that by explaining what presets mean acoustically ('speech' lifts dialogue, 'night' tames explosions while keeping voices), which helps the agent choose a value rather than just pass one.

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?

States a specific verb and resource ('Apply a named equaliser curve') plus a disclosed side effect ('switch the equaliser on'). It names the discovery sibling equalizer_presets, so an agent can distinguish this mutation tool from the listing tool without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes enumeration to equalizer_presets ('to see what exists and what each is for') and maps the two most common user intents ('can't hear the dialogue') to the 'speech' and 'night' presets. That is concrete when-to-use guidance with a named alternative.

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

Deploy Server

Other Tools