Save the current FX settings on a track as a named preset, allowing you to reuse effect configurations quickly.
Save the current FX settings as a preset.
Args: preset_name: Name for the new preset.
| Name | Required | Description | Default |
|---|---|---|---|
| fx_index | Yes | ||
| preset_name | Yes | ||
| track_index | Yes |
Changes observed during successful MCP inspections.
v1.7.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no side-effect detail beyond the destructiveHint annotation. It does not mention whether an existing preset with the same name is overwritten, whether the save persists to disk, or what other state may be affected.
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 short, front-loaded with the purpose, and contains no filler. However, the Args section lists only one of three required parameters, which is misleading but not a conciseness failure.
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?
For a destructive, three-parameter tool with no output schema, the description is materially incomplete. It omits the meaning of track_index/fx_index and any behavior around preset overwrites or persistence, so an agent cannot reliably invoke it.
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?
Only preset_name is explained. The required track_index and fx_index parameters have no schema descriptions and are not explained in the description, leaving the agent unable to determine how to target the FX to save.
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 names a specific operation ('Save...as a preset') and resource ('current FX settings'), which is distinct from the get/set preset siblings. It does not explicitly differentiate from those siblings, and 'current FX settings' is ambiguous because the tool actually takes track_index and fx_index arguments.
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?
The description gives no guidance about when to use this tool versus related tools such as set_fx_preset or get_fx_preset. There are no stated preconditions, alternatives, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.