Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

remove_audio_bus

Removes an audio bus by name to eliminate unused audio channels from the Godot project.

Instructions

Remove an audio bus by name.

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": {
      "name": "<name>"
    },
    "name": "remove_audio_bus"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBus name to remove

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 provided, so the description carries the full burden and does not meet it. It implies a destructive operation but says nothing about whether removal is reversible, what happens to effects or players routed through the bus, whether it requires the bus to exist, or what error behavior to expect for an unknown name.

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?

One front-loaded sentence with no filler or redundancy. It is arguably too terse for a destructive tool, but there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter tool with fully documented schema, the core invocation information is present. However, with no annotations and no output schema, the description should have disclosed the destructive/reversibility profile and any side effects on bus routing, which it does not.

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

Parameters3/5

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

Schema coverage is 100% and the only parameter already documents 'Bus name to remove', so the description adds nothing beyond confirming name-based identification. Baseline 3 applies when the schema does the heavy lifting.

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 states a specific verb and resource ('Remove an audio bus') and even names the identifier used ('by name'), so the action is unambiguous and naturally distinguished from the sibling add_audio_bus. It lacks any explicit mention of how it differs from other bus-related siblings like set_audio_bus_volume, but the destructive verb makes the distinction obvious.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no pointer to alternatives. An agent must infer that this is the counterpart to add_audio_bus purely from the verb.

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

Deploy Server

Other Tools