Skip to main content
Glama

equalizer_set

Adjust audio equalizer bands, gain, preamp, and normalization to shape playback sound; set a full ten-band curve in one call or switch the EQ on/off without losing it.

Instructions

Adjust the equaliser. Set one band with band (0-9, low to high) plus gain in dB, or the whole curve at once with bands. enabled switches the equaliser in and out without discarding the curve, normalize evens out quiet dialogue against loud action, and preamp makes headroom so boosted bands don't clip. Gains are clamped to ±12 dB. Every change rebuilds mpv's audio filter chain, so set a whole curve in one call rather than nine.

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": "equalizer_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
bandNoBand index 0-9: 31, 62, 125, 250, 500, 1000, 2000, 4000, 8000, 16000 Hz
gainNoGain in dB for that band, -12 to 12
bandsNoAll ten gains in dB, low frequency first
preampNoPreamp in dB, -20 to 12
enabledNoSwitch the equaliser on or off, keeping the curve
normalizeNoDynamic loudness normalisation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the ±12 dB clamp, that `enabled` toggles without discarding the curve, and the significant side effect that every change rebuilds mpv's audio filter chain. Remaining gaps are persistence across sessions/playback state and error behavior when no audio is active.

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?

Front-loaded with the action and mode split, then per-parameter roles, then the clamp and the performance caveat. Every sentence conveys information an agent needs and nothing is repeated.

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 6-parameter mutation tool with no annotations and no output schema, the description covers all parameters, the clamping constraint, and the cost of repeated calls. It could be more complete by stating what a call returns or whether changes persist across tracks, but the essentials for correct invocation are present.

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; the description goes beyond by explaining that band indices run low to high, that `normalize` evens quiet dialogue against loud action, and that `preamp` exists to create headroom against clipping. This adds real intent-level meaning rather than restating the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Adjust the equaliser') and immediately enumerates the two operating modes (single band via `band`+`gain`, or whole curve via `bands`). It does not name any sibling such as equalizer_get or equalizer_reset, so differentiation is only implicit, which puts it just short of a 5.

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?

Gives concrete operating guidance: use `band`+`gain` for one band, `bands` for the whole curve, and 'set a whole curve in one call rather than nine' explicitly steers batching behavior. It stops short of saying when to prefer this over equalizer_preset or equalizer_reset, and no exclusions are stated.

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