Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_audio_info

Retrieve audio node properties and configuration data from Godot Engine projects for AI-assisted debugging and scene analysis.

Instructions

Get audio node information. (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": "get_audio_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations provided, the description carries full behavioral burden. While 'Get' implies a read-only operation, the description discloses nothing about return value structure, what 'compatibility' implies for behavior, or why timeoutMs/autoConnect parameters exist for an information getter.

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?

Extremely brief at 6 words, but this efficiency crosses into under-specification. The single sentence conveys the basic operation type, yet wastes the parenthetical on an unexplained 'Compatibility' label instead of useful behavioral context.

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?

Severely incomplete given zero annotations, zero schema descriptions, and no output schema. The description does not compensate for missing metadata by explaining return values, error conditions, or the specific audio node types supported (e.g., AudioStreamPlayer vs AudioStreamPlayer2D).

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 parameters. The description completely fails to explain what these parameters control, why a 'get info' tool needs connection timeouts, or what autoConnect=true connects to. Critical gap given zero schema documentation.

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?

States it retrieves 'audio node information' which distinguishes it from sibling get_audio_bus_layout, but 'audio node' is ambiguous in the Godot context (AudioStreamPlayer? Audio bus?). The '(Compatibility tool)' parenthetical adds confusion without clarifying scope or deprecation status.

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?

Provides no guidance on when to use this versus get_audio_bus_layout or other audio inspection tools. The '(Compatibility tool)' notation hints at special usage constraints but fails to explain what they are or suggest alternatives.

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