Control whether an FX plugin on a specific track is enabled or disabled by setting its bypass state using track and FX indices.
Enable or bypass (disable) an FX plugin on a track.
| Name | Required | Description | Default |
|---|---|---|---|
| bypassed | Yes | ||
| fx_index | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description indicates a direct set action, but does not clarify if it toggles or sets to the given state, nor does it mention side effects or permissions. With no annotations, more detail would be beneficial.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, concise sentence with no wasteful words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks context on indexing (0-based?), success/failure behavior, and required prior steps (e.g., track must have FX). With no output schema and limited annotations, it is insufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Parameters have clear names (track_index, fx_index, bypassed), but the description adds no additional meaning. With zero schema description coverage, more elaboration is needed to clarify indexing and boolean meaning.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool enables or bypasses an FX plugin on a track, specifying the verb and resource. It distinguishes from siblings like remove_fx (removes) and add_fx (adds).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives (e.g., get_fx_parameters to check current state). No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.