Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

eq_low_pass

Applies a lowpass filter to a track at a specified frequency to darken or muffle its sound.

Instructions

Add a lowpass filter at freq Hz to a track for darkening/muffling.

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

Input Schema

NameRequiredDescriptionDefault
qNo
freqNo
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description alone carries the burden. It clearly says the tool adds a filter at a frequency, but it does not mention side effects, non-destructive nature, or how the `q` parameter affects behavior. It is accurate but minimal.

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?

A single, concise sentence that conveys the essential information without any filler or redundant phrases. It is well-structured and easy to parse.

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 simple filter operation, the description provides sufficient context: what it does, where it applies (track), and the key parameter. It does not mention output or potential side effects, but given the simplicity of the tool and the lack of an output schema, this is acceptable.

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

Parameters3/5

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

The description explains `freq` explicitly and `track_id` implicitly ('to a track'), but `q` is not mentioned at all. Schema coverage is roughly 66%, which is not high enough to warrant a baseline of 3, and the description does not compensate for the missing parameter.

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 action ('add a lowpass filter') and the purpose ('darkening/muffling'), including the key parameter `freq` in Hz. It also implicitly distinguishes itself from sibling tools like eq_high_pass or eq_tilt by specifying a lowpass filter.

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

Usage Guidelines3/5

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

The description gives the intended use case (darkening/muffling) but does not explicitly state when to use this tool over alternatives (e.g., eq_high_pass) or when not to use it. The guidance is implicit rather than explicit.

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