Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

set_audio_bus_volume

Set an audio bus volume in dB by bus name to control mix levels in Godot.

Instructions

Set the volume of an 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>",
      "volume_db": "<volume_db>"
    },
    "name": "set_audio_bus_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesBus name
volume_dbYesVolume in dB

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 behavioral burden and fails to do so. It does not state the accepted dB range or clamping behavior, whether the change is immediate or persisted, whether it requires playback to be stopped, or whether the call can fail for a missing bus.

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?

A single short sentence with the verb and resource front-loaded, so nothing is wasted. However, the brevity is under-specification rather than efficiency: the one sentence cannot cover what an agent needs to invoke a mutation tool confidently.

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?

The tool is simple (2 required params, no nesting, no output schema), which lowers the bar, but with no annotations and no mention of valid ranges or side effects, the definition leaves real gaps. A brief note on dB bounds and persistence would make it complete.

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% (both name and volume_db are documented in the schema), so the parameter baseline is 3. The description adds no meaning beyond the schema, such as valid dB bounds or whether volume_db is linear gain versus decibels.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Set the volume of an audio bus" only restates the tool name (set_audio_bus_volume) in sentence form; it adds no scope, units, or distinguishing detail. It is not misleading, but it gives an agent nothing beyond what the identifier already conveys.

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 when-to-use guidance is present. Nothing tells the agent when to prefer this over related operations such as add_audio_bus_effect or batch_set_property, nor whether the bus must already exist or whether it affects currently playing audio.

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