Skip to main content
Glama

game_light_2d

Create and configure 2D point or directional lights and light occluders for your Godot game scenes.

Instructions

Create/configure 2D lights and light occluders

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoNode name
colorNoLight color {r,g,b,a}
rangeNoLight texture range
actionYesAction: create_point, create_directional, create_occluder
energyNoLight energy
pointsNoOccluder polygon points [{x,y},...] (for create_occluder)
nodePathNoNode path (for configure)
parentPathNoParent node path
Behavior2/5

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

No annotations provided. The description lacks details on side effects, permissions, or behavioral traits beyond stating 'create/configure'. For a resource creation tool, more transparency is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, no unnecessary words. Highly concise and front-loaded.

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?

Despite full schema coverage, the description is too brief for a tool with 8 parameters and no output schema. It does not explain the difference between actions or how to use the tool effectively.

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%, so baseline is 3. The description does not add extra meaning beyond the schema parameter descriptions, but that is acceptable given full coverage.

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?

The description clearly states the purpose: creating and configuring 2D lights and light occluders. It uses specific verbs and resource, and distinguishes from sibling tools like game_light_3d.

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?

No guidance on when to use this tool vs alternatives. With many sibling tools (e.g., game_light_3d, game_environment), explicit usage context is missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tugcantopaloglu/godot-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server