Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_audio_player

Add an AudioStreamPlayer node to a Godot scene, routing a res:// audio stream to a chosen parent node and audio bus.

Instructions

Add an AudioStreamPlayer node to the scene.

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

Input Schema

NameRequiredDescriptionDefault
busNoAudio bus name to route to
parent_pathNoParent node path
stream_pathNores:// path to the audio stream

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?

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not say whether an open scene is required, where the node lands when parent_path is omitted, whether the operation is undoable, or what the call returns. For a mutation 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.

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity comes at the cost of the behavioral and usage detail noted elsewhere.

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 an unannotated mutation tool with no output schema, the definition leaves the agent guessing about scene prerequisites, default parenting, and the returned value. The schema covers the inputs well, but the surrounding behavioral context needed to invoke it confidently is absent.

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%, so all three parameters are already self-documenting, and the baseline of 3 applies. The description adds no syntax, defaults, or routing detail, and the phrase "to the scene" slightly muddies the role of parent_path.

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 an AudioStreamPlayer node"), which is unambiguous on its own. It does not distinguish itself from the generic sibling add_node or batch_add_nodes, so an agent must infer which to prefer 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 mention of prerequisites, and no reference to alternatives such as add_node or batch_add_nodes for bulk creation. The only context is the implied one that the caller wants an audio player rather than some other node type.

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