Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_world_environment

Adds a WorldEnvironment node with a sky to a Godot scene, enabling environment lighting and sky effects for your game.

Instructions

Add a WorldEnvironment node with a sky 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_world_environment"
  }
}

Input Schema

NameRequiredDescriptionDefault
sky_typeNoSky type (ProceduralSkyMaterial, etc.)
parent_pathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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 the entire behavioral burden. It implies a scene mutation but says nothing about what happens if parent_path is omitted or invalid, whether an existing WorldEnvironment is replaced, whether the operation is reversible, or what is returned. For a mutation tool with zero annotation coverage this is a meaningful 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?

One sentence, front-loaded with the verb and resource, with no filler. It is efficiently written, though the brevity leaves gaps addressed in other dimensions rather than being a conciseness fault.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a low-complexity tool with two optional, fully documented parameters and no output schema, so the description needn't explain return values. Still, it omits defaults for both optional parameters and any relationship to add_node, leaving the agent to guess at call-time behavior.

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

Parameters2/5

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

Schema description coverage is 100%, so the schema already documents both parameters; the baseline would be 3. However, the description adds no meaning whatsoever about sky_type choices or the default parent, so it does nothing to reduce ambiguity around behavior like defaulting the sky type or attaching at scene root.

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 a specific resource ('WorldEnvironment node with a sky'), plus the target ('the scene'), so the agent knows exactly what will be created. It stops short of distinguishing this from the sibling add_node, which could also create nodes, so it does not fully earn a 5.

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 instead of add_node or another node-creation tool, no prerequisites, and no exclusions. The agent must infer usage entirely from the tool name.

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