Skip to main content
Glama

effect_wahwah

Apply a wah-wah modulation effect to selected audio, using adjustable LFO frequency, phase, depth, resonance, and offset to create controlled filter sweeps.

Instructions

Apply wahwah effect to the selected audio.

Args: frequency: LFO frequency in Hz (0.1-4.0). Default: 1.5 phase: LFO start phase (0-360). Default: 0 depth: Modulation depth (0-100). Default: 70 resonance: Resonance (0.1-10). Default: 2.5 offset: Frequency offset (0-100). Default: 30

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
depthNo
phaseNo
offsetNo
frequencyNo
resonanceNo
Install Server

TDQS

C2/5.0
Behavior1/5

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

The description does not disclose side effects, whether the effect is destructive, or how it interacts with the selection. No annotations (e.g., destructiveHint) provide additional clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is minimal and to the point, but it lacks structural organization (e.g., sections or parameter explanations). It is concise without being overly verbose, but could be better structured.

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

Completeness1/5

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

The description provides insufficient context to understand how the parameters interact or what the effect does beyond a generic statement. With zero schema coverage, it is incomplete for a user to effectively use the tool.

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

Parameters1/5

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

Parameter names are listed with defaults but their meanings and impact on the effect are not explained. The schema also lacks descriptions, leaving the user without any semantic understanding of the parameters.

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?

The description clearly states the action 'Apply wahwah effect' and the target 'selected audio'. It is specific enough to convey the tool's primary function, though it does not elaborate on what the wahwah effect entails.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this effect versus similar effects (e.g., phase, tremolo). There is no mention of suitable contexts or conditions that would favor this tool.

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

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/FFriends/MCP-Audacity'

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