Skip to main content
Glama

effect_adjustable_fade

Apply a customizable audio fade by selecting fade direction (in or out) and curve shape (linear, exponential, or logarithmic) for precise control over volume changes.

Instructions

Apply an adjustable fade with curve control.

Args: fade_type: 0=fade up (in), 1=fade down (out). Default: 0 curve: Curve shape (0=linear, positive=exponential, negative=logarithmic). Default: 0

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curveNo
fade_typeNo
Behavior2/5

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

No annotations are provided. The description discloses parameter values but does not mention side effects, destructiveness, reversibility, or prerequisites (e.g., a selection needed). For a mutation tool, this is insufficient transparency.

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?

The description is brief with two focused paragraphs. The first sentence clearly states the purpose. Every sentence adds value, with an efficient args format. No wasted words.

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

Completeness2/5

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

The tool has optional parameters, no annotations, no output schema. The description lacks context about what audio is affected (selected clip/region?), reversibility, undo support, and valid curve range. More details are needed for full comprehension.

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

Parameters5/5

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

Schema coverage is 0%, so the description fully compensates by explaining the meaning of both parameters: fade_type values (0=in, 1=out) and curve values (0=linear, +exp, -log). This adds significant value beyond the schema's type and default.

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 tool applies a fade with adjustable curve control. The verb 'apply' and resource 'fade' are explicit, and the detail on curve control distinguishes it from simpler fade siblings like effect_fade_in and effect_fade_out.

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?

Defaults are provided, but no explicit guidance on when to use this vs. dedicated fade tools, when not to use it, or prerequisites. Usage is implied but not fully clarified.

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

Install Server

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/robworks-code/audacity-mcp-max'

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