Skip to main content
Glama

game_light_2d

Create and configure 2D point lights, directional lights, and light occluders with settings for color, energy, range, and parent path.

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
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; description does not disclose behavioral traits like whether it is destructive, permission requirements, or side effects. The brief description does not compensate for missing annotations.

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?

The description is very concise (5 words) and front-loaded, but for a tool with multiple actions and nested parameters, a bit more detail would improve usability without being verbose.

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?

Given the tool's complexity (7 parameters, 3 actions, nested object) and no output schema or annotations, the description is too sparse to be complete. It does not explain actions, configuration, or return values.

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% with parameter descriptions. The tool description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 clearly states the tool creates/configures 2D lights and light occluders, distinguishing it from 3D lighting 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 versus alternatives such as game_light_3d or game_gi. The description does not provide context for selection.

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