Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_audio_player

Add an AudioStreamPlayer node to Godot scenes to enable audio playback for games and interactive applications.

Instructions

Add AudioStreamPlayer node. (Compatibility tool)

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
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 full disclosure burden. It mentions 'Compatibility tool' as a behavioral trait but fails to explain what this means in practice (e.g., different internal initialization, deprecated API usage). No mention of side effects, node placement context, or lifecycle implications.

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?

Extremely brief at two sentences. The main action is front-loaded in the first sentence, and the second sentence attempts to add context (albeit unclearly). Given the severe information gaps elsewhere, it is appropriately terse in structure but undersized for the content required.

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?

With 2 undocumented parameters, no annotations, and no output schema, the description should explain the 'Compatibility' aspect and parameter meanings. It leaves critical gaps: why use this instead of add_node with type AudioStreamPlayer, what the timeout applies to, and what auto-connect targets.

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

Parameters1/5

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

Schema description coverage is 0% for both 'timeoutMs' and 'autoConnect', yet the description provides no parameter context whatsoever. It fails to explain what operation times out, what connection is automatically established, or what values are appropriate beyond the schema's minimum constraint.

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

Purpose3/5

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

The description states the basic action (Add) and resource (AudioStreamPlayer node), but the parenthetical '(Compatibility tool)' is unexplained and confusing. It doesn't clarify whether this is for backward compatibility, Godot's compatibility rendering mode, or compatibility with specific audio formats, weakening clarity.

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 explicit guidance on when to use this tool versus the generic 'add_node' sibling or when to prefer 'add_audio_bus' for audio routing. The 'Compatibility tool' label might imply legacy usage but is too vague to constitute actionable guidance.

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