Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

setup_environment

Configure Godot world environment settings to manage lighting, sky effects, and atmospheric rendering for game scenes through the MCP Bridge.

Instructions

Configure world environment. (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": "setup_environment"
  }
}

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?

No annotations are provided, so the description carries full disclosure burden. It fails to mention that additionalProperties: true allows arbitrary configuration keys, what the timeoutMs applies to (connection? command execution?), or what autoConnect connects to. The compatibility warning is the only behavioral hint.

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 two fragments, but brevity here masks under-specification rather than efficient communication. The sentences are front-loaded but fail to earn their place due to vagueness.

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?

Inadequate for a configuration tool with dynamic parameters (additionalProperties: true) and no output schema. Lacks explanation of what 'world environment' encompasses, what the compatibility layer preserves, and how the timeout/autoConnect parameters affect operation.

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, and the description completely omits what these parameters control. It also fails to document the significance of additionalProperties: true, which permits arbitrary extra configuration fields.

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?

Provides a verb ('Configure') and resource ('world environment'), but remains ambiguous in the Godot context—unclear if this configures the WorldEnvironment node, general project settings, or something else. The '(Compatibility tool)' parenthetical adds some distinction but is cryptic.

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 '(Compatibility tool)' notation implies legacy usage but fails to explicitly state when to use this versus siblings like setup_lighting or set_project_setting, or what 'compatibility' refers to (API version? Godot 3 vs 4?).

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