Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_audio_bus_layout

Retrieves the current audio bus layout, including buses, effects, and volume settings, so you can inspect and verify your Godot project's audio configuration.

Instructions

Get the current audio bus layout (buses, effects, volumes).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_audio_bus_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. The word 'Get' and 'current' imply a non-mutating snapshot read with no side effects, and the parenthetical tells the agent what categories of data come back, but it never explicitly states read-only/non-destructive behavior or whether the returned layout reflects pending unsaved editor state.

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

Conciseness5/5

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

A single front-loaded sentence naming the resource first and the payload second, with zero filler. Nothing could be removed without losing information.

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

Completeness4/5

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

For a zero-parameter read getter with no output schema, the parenthetical enumeration of returns (buses, effects, volumes) is the key compensating detail an agent needs to know this is worth calling. Only a brief note on whether the snapshot is editor-live versus saved would make it complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on arguments.

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?

States a specific verb (Get) and resource (audio bus layout), and the parenthetical enumerates what the layout comprises: buses, effects, volumes. This clearly reads as the read-only inspection counterpart to the mutating siblings add_audio_bus/set_audio_bus_volume, though it doesn't name an alternative explicitly.

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?

Usage is only implied: an agent can infer this is the tool for inspecting the current bus setup, presumably before or after mutations. There is no explicit when-to-use, no stated preconditions, and no routing to siblings such as get_node_properties or get_performance_monitors.

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