Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_audio_bus_effect

Add an audio effect to a specified Godot audio bus by providing its bus name and effect class.

Instructions

Add an audio effect to a bus.

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": {
      "bus_name": "<bus_name>",
      "effect_type": "<effect_type>"
    },
    "name": "add_audio_bus_effect"
  }
}

Input Schema

NameRequiredDescriptionDefault
bus_nameYesTarget bus name
effect_typeYesEffect class name (e.g. AudioEffectReverb)

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 supplied, the description carries the full behavioral burden, yet it says nothing about whether the effect takes effect immediately, is persisted, or is undoable. Failure modes — unknown bus_name or invalid effect_type — are also unmentioned.

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 the brevity comes at the cost of the guidance noted in other dimensions.

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?

This is a mutation tool with no annotations and no output schema, so the description should explain effects of the change and expected response. It provides none of that, leaving an agent with only the bare action.

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%, with both bus_name and effect_type documented inline including an example class name. The description adds no meaning beyond the schema, so the baseline 3 applies.

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 states a specific verb ('Add') and resource ('an audio effect to a bus'), so the operation is unambiguous. It does not, however, distinguish itself from nearby siblings such as add_audio_bus, which an agent could easily confuse with effect addition.

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 guidance on when to use this versus alternatives, no prerequisites (e.g., that the bus must already exist), and no note on ordering or duplicate effects. The agent must infer all usage conditions.

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