Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_audio_bus

Creates a new audio bus in Godot with a specified name and initial volume in dB, enabling organized game audio routing.

Instructions

Add a new audio bus.

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": "add_audio_bus"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBus name
volume_dbNoInitial volume in dB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 behavioral burden, and it discloses almost nothing: not whether the bus is persisted, whether the name must be unique, whether the change is undoable, or what happens if a bus with that name already exists. For a mutating tool with zero annotation coverage this is a significant gap.

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

Conciseness3/5

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

One short sentence with no wasted words, which is appropriately front-loaded, but the terseness crosses into under-specification rather than genuine conciseness. There is no structure covering behavior or result.

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 mutating tool with no annotations and no output schema, the description should state side effects and at least whether the new bus is returned or must be fetched. Nothing about return value, persistence, or duplicate-name handling is covered, so an agent cannot call it with confidence.

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 description coverage is 100%, with both 'name' and 'volume_db' documented in the schema itself, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as default volume behavior when volume_db is omitted.

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 gives a specific verb and resource ('Add a new audio bus'), so an agent knows exactly what operation is performed. It does not distinguish itself from siblings such as add_audio_bus_effect or set_audio_bus_volume, leaving the agent to infer the difference from names alone.

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 guidance, no prerequisite (e.g. an open scene or project), and no mention of alternatives like add_audio_bus_effect or set_audio_bus_volume. The description is purely a restatement of the operation.

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