Skip to main content
Glama

fx_set_param_by_name

Set an effect parameter on a track's FX chain by matching the parameter name (fuzzy) and applying a normalized value.

Instructions

Set FX parameter by name (fuzzy match).

Args: track_index: 0-based track index. fx_index: 0-based FX chain index. param_name: Parameter name or partial match. value: 0.0-1.0 normalized.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
fx_indexYes
param_nameYes
valueYes
Behavior3/5

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

Mentions fuzzy match and value range. No annotations. Lacks details on multiple matches or error handling.

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 concise lines: purpose then parameter list. No wasted words.

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?

Covers essential parameter meanings. Minor gaps: no output info, fuzzy match behavior not fully explained.

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 has 0% coverage. Description adds meaning: 0-based indexes, partial match for name, normalized value range.

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?

Clear verb ('Set FX parameter') and resource ('by name (fuzzy match)'). Distinct from sibling like fx_set_param which likely uses index.

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?

Parameter details provided. Implicitly when you want to set by name vs index, but no explicit when-not or alternatives.

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/xDarkzx/Reaper-MCP'

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