Skip to main content
Glama

remove_effect

Remove an audio effect from its processing chain by providing the effect's GUID.

Instructions

Remove an effect from its chain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
effect_guidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core handler: executes FMOD Studio script that finds an effect by GUID using _FIND_EFFECT_HELPER JS helper, calls deleteObject(hit.effect) to remove it from its chain, and returns {removed, guid, type, target_path}.
    async def remove_effect(client: StudioClient, effect_guid: str) -> dict[str, Any]:
        js = (
            _FIND_EFFECT_HELPER
            + f"""
            var hit = __mcp_findEffect({json.dumps(effect_guid)});
            if (!hit) throw new Error("Effect not found for guid: " + {json.dumps(effect_guid)});
            var path = hit.target_path;
            var type = hit.effect.entity;
            studio.project.deleteObject(hit.effect);
            return {{ removed: true, guid: {json.dumps(effect_guid)}, type: type, target_path: path }};
        """
        )
        return await client.eval(js)
  • Tool registration: decorated with @mcp.tool() exposing the tool to MCP clients. Calls effects.remove_effect with the studio client.
    @mcp.tool()
    async def remove_effect(effect_guid: str) -> dict[str, Any]:
        """Remove an effect from its chain."""
        return await effects.remove_effect(_studio(), effect_guid)
  • JavaScript helper _FIND_EFFECT_HELPER: walks all bus effect chains (master + descendants) and all event tracks (master + group) to locate an effect by GUID. Used by remove_effect and other effect tools.
    _FIND_EFFECT_HELPER = r"""
    function __mcp_findEffect(guid) {
        function scanChain(chain, target_path) {
            if (!chain || !chain.effects) return null;
            for (var j = 0; j < chain.effects.length; j++) {
                if (chain.effects[j].id === guid) {
                    return { effect: chain.effects[j], chain: chain, index: j, target_path: target_path };
                }
            }
            return null;
        }
        /* Master bus + descendant buses (walk mixer tree) */
        function walkBus(bus) {
            if (!bus || !bus.isValid) return null;
            var hit = scanChain(bus.effectChain, bus.getPath());
            if (hit) return hit;
            var rel = bus.relationships && bus.relationships.items;
            var children = rel && rel.destinations;
            if (children) for (var i = 0; i < children.length; i++) {
                var h = walkBus(children[i]);
                if (h) return h;
            }
            return null;
        }
        var hit = walkBus(studio.project.workspace.mixer.masterBus);
        if (hit) return hit;
        /* All event tracks */
        var events = studio.project.model.Event.findInstances();
        for (var i = 0; i < events.length; i++) {
            if (!events[i].isValid) continue;
            var tracks = [events[i].masterTrack];
            if (events[i].groupTracks) for (var t = 0; t < events[i].groupTracks.length; t++) tracks.push(events[i].groupTracks[t]);
            for (var t = 0; t < tracks.length; t++) {
                if (!tracks[t]) continue;
                var mg = tracks[t].mixerGroup;
                if (!mg || !mg.effectChain) continue;
                var label = events[i].getPath() + (t === 0 ? "#track=master" : "#track=" + (t-1));
                var h = scanChain(mg.effectChain, label);
                if (h) return h;
            }
        }
        return null;
    }
Behavior2/5

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

Without annotations, the description must disclose behavioral traits. It only indicates a destructive operation ('remove') but omits details like prerequisites, reversibility, or side effects on the audio chain.

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

Conciseness4/5

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

The description is exceptionally concise at 6 words, with no unnecessary content. However, it may be too sparse to convey adequate information.

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?

Given the tool's simplicity (one parameter, no annotations, but an output schema exists), the description lacks critical context such as expected return value or effect on the project. It is insufficient for safe autonomous invocation.

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?

The single parameter 'effect_guid' is not mentioned or explained in the description. With 0% schema description coverage, the agent receives no semantic help beyond the type and requirement from the schema.

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 (removing) and the resource (an effect from its chain). It effectively distinguishes from sibling tools like add_effect or bypass_effect. However, 'its chain' is somewhat ambiguous and could be more precise.

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

Usage Guidelines2/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 tool versus alternatives such as bypass_effect or when not to use it. The description offers no context for decision-making.

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/jmperez127/fmod-mcp'

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