Godot MCP Server Ultimate Edition

by Dex865378

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

create_audio_player

Add an audio player node to a Godot scene, optionally configuring spatial audio, volume, autoplay, and bus settings.

Instructions

Create an AudioStreamPlayer or AudioStreamPlayer3D node with optional audio file and configuration.

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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>"
    },
    "name": "create_audio_player"
  }
}

Input Schema

Name	Required	Description
`projectPath`	Yes	Path to the Godot project directory
`scenePath`	Yes	Scene file path
`parentPath`	No	Parent node path (default: root)
`audioPath`	No	Path to audio file (.ogg/.wav/.mp3), relative to project
`options`	No	Options: { spatial: bool, volume_db: float, autoplay: bool, bus: string }

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states basic creation capabilities without disclosing side effects like overwriting nodes, permission requirements, or error handling for invalid paths.

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?

The description is a single concise sentence that communicates the core purpose without any wasted words. It is well-structured and front-loaded with the key action.

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?

Given 5 parameters (including a nested object) and no output schema, the description omits important context like return values, whether the node is automatically added to the scene, or prerequisites such as scene existence. It is incomplete for effective tool usage.

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%, so baseline is 3. The description adds minimal extra meaning, just reiterating 'optional audio file and configuration' without enhancing understanding beyond the schema's parameter descriptions.

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

Purpose5/5

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

The description clearly states the tool creates an AudioStreamPlayer or AudioStreamPlayer3D node with optional audio file and configuration. It specifies the verb 'create' and the resource, distinguishing it from generic node tools like 'add_node'.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'add_node' or 'create_timer'. No explicit context or exclusions are given, leaving the agent to infer usage without comparison.

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

Deploy Server