Skip to main content
Glama

equalizer_get

Read the 10-band equaliser state: band gains, centre frequencies, preamp, loudness normalisation, and active filter chain. Check it before changing bands to adjust the user's curve instead of replacing it.

Instructions

Read the 10-band equaliser: per-band gains in dB, the band centre frequencies they correspond to, the preamp, whether loudness normalisation is on, and the filter chain mpv is actually running. Read this before changing a band so you adjust the user's curve instead of replacing it.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 load, and it does disclose that the response reflects the filter chain mpv is 'actually running' – i.e. live runtime state, not just stored config. It also implies the read-modify-write relationship with the mutating equalizer tools. It stops short of stating permissions or whether unset bands are reported.

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?

Two sentences, both earning their place. The return contents are front-loaded and the workflow rationale follows immediately, with no hedging or restated tool name padding it out.

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?

There is no output schema and no annotations, so the description must describe the return value itself – and it largely does, listing five distinct pieces of state. Minor gaps remain: band ordering, how disabled or flat bands appear, and whether the filter chain is returned as raw strings are not covered.

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?

The tool takes no parameters, so there is nothing for the description to clarify beyond the schema. The description instead spends its words on return-value semantics such as dB units and band centre frequencies, which is the right use of space for a zero-parameter tool.

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 names a specific verb and resource ('Read the 10-band equaliser') and then enumerates exactly what comes back: per-band gains in dB, band centre frequencies, preamp, loudness normalisation, and the running filter chain. That enumeration makes it unmistakable against siblings such as equalizer_set, equalizer_reset, and equalizer_preset.

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?

It gives a clear when-to-use rule: read before changing a band so you modify the user's curve rather than replace it. That is a concrete precondition tied to a real workflow. It does not name equalizer_set explicitly as the alternative, but the guidance is unambiguous without it.

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