Skip to main content
Glama

fusion_tool_delete

Removes a Fusion tool from a composition, or bypasses and unbypasses it to keep the node while disabling its effect. Use it to clean up node graphs or toggle tool behavior without deleting.

Instructions

Delete a Fusion tool, or bypass/unbypass it (bypass=true/false keeps it).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tool_name": "<tool_name>"
    },
    "name": "fusion_tool_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNocurrent
compNo
bypassNo
tool_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints that bypass preserves the tool, but never states that default behavior is destructive and irreversible, whether the tool must be unbypassed before deletion, or what happens if the name is not found. That is a large gap for a mutating tool.

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?

A single front-loaded sentence with no filler, and the dual-mode caveat is attached directly to the operation. The phrase 'bypass/unbypass it' is slightly compressed but readable.

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?

For a four-parameter mutating tool with no annotations and no output schema, the definition leaves too much open: two parameters are undocumented, the destructive default is unstated, and the response is not characterized. It is not sufficient to call the tool confidently.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters. The description covers only 'bypass' semantics and implies 'tool_name'; 'clip' (default 'current') and 'comp' (default null) are left entirely unexplained in both schema and description, so the agent cannot know what they scope.

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 names a specific verb and resource (delete a Fusion tool) and discloses a second mode (bypass/unbypass). It does not explain how this differs from the sibling fusion_tool_add or where a tool lives, but an agent can tell this is the tool-removal operation.

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?

The parenthetical '(bypass=true/false keeps it)' implies the when-to-use split: bypass instead of delete when the tool should be preserved. There is no explicit guidance on when bypass is preferable, no prerequisites, and no mention of which clip/comp context matters.

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