Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_lighting

Add a light node to a Godot scene by choosing the light type and optionally setting the parent path and property overrides for AI-driven game development.

Instructions

Add a light node to the scene.

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": {
      "light_type": "<light_type>"
    },
    "name": "setup_lighting"
  }
}

Input Schema

NameRequiredDescriptionDefault
light_typeYesLight type (DirectionalLight3D, OmniLight3D, SpotLight3D)
propertiesNoLight property overrides
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 supplied, so the description carries the full behavioral burden. It implies a scene mutation but says nothing about whether the node is persisted or undoable, what happens when parent_path is invalid, or what the tool returns (a node path?), which is a significant gap for a creation tool with no output schema.

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?

A single clean sentence with no filler, but it is under-specified rather than concise; the one sentence carries no operational detail beyond the name.

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?

For a mutating tool with a nested override object, no annotations, and no output schema, one sentence is not enough. An agent gets no information about the override semantics, required parent context, or the result of the call.

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 description coverage is 100% and all three parameters are documented there, so baseline 3 applies. The description adds nothing about light_type choices, the meaning of the freeform properties override object, or parent_path resolution, but it does not need to given the schema.

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?

States a specific verb and resource: "Add a light node to the scene." That distinguishes it from the setup_camera_3d/setup_collision family by resource, but it never says how it differs from the generic add_node or batch_add_nodes siblings, so an agent must guess at the boundary.

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 when-to-use guidance, no prerequisites (e.g. an open scene or a valid parent), and no mention of when an agent should prefer add_node or batch_add_nodes instead. Usage is only implied by 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