Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_light_3d

Create and configure 3D directional, omni, and spot lights in Godot; set color, energy, range, shadows, and spot angle for scene lighting.

Instructions

Create/configure 3D lights (directional/omni/spot)

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": {
      "action": "<action>"
    },
    "name": "game_light_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNode name
colorNoLight color {r,g,b}
rangeNoLight range (omni/spot)
actionYesAction: create or configure
energyNoLight energy/intensity
shadowsNoEnable shadow casting
nodePathNoNode path (for configure)
lightTypeNoType: directional, omni, spot
spotAngleNoSpot cone angle in degrees
parentPathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions create/configure but does not explain whether configure requires an existing node, whether create also updates, what happens on overwrites, or what side effects occur. This is under-disclosed for a mutating tool.

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?

The description is a single efficient sentence with the key verb and resource front-loaded. It has no wasted words, though it is so brief that it leaves important behavioral and contextual details to the schema.

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 tool with 10 parameters, no output schema, and no annotations, the description is incomplete. It does not explain required parameter combinations, the difference between create and configure flows, or what the tool returns. An agent would need to infer too much to invoke it confidently.

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%, so the schema already documents all parameter meanings. The description adds a light organizational context but does not clarify parameter interactions, such as which fields apply to create versus configure. Baseline 3 is appropriate because the schema handles the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states a specific verb pair ('Create/configure') with a clear resource ('3D lights') and enumerates the supported subtypes (directional/omni/spot). The '3D' qualifier distinguishes it from the sibling game_light_2d, so an agent can identify its scope.

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 description gives no guidance on when to choose this tool over alternatives such as game_light_2d, game_environment, or game_gi, and provides no exclusions or conditions. Usage context is only implied by the tool's name and stated purpose.

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