Skip to main content
Glama

game_environment

game_environment

Get or set Godot scene environment and post-processing properties such as background, fog, glow, and tonemap.

Instructions

Get or set environment and post-processing settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoAction: get or set. Default: set
contrastNoContrast adjustment
glowBloomNoGlow bloom
brightnessNoBrightness adjustment
fogDensityNoFog density
fogEnabledNoEnable fog
saturationNoSaturation adjustment
ssaoRadiusNoSSAO radius
ssrEnabledNoEnable SSR
glowEnabledNoEnable glow
ssaoEnabledNoEnable SSAO
tonemapModeNo0=linear, 1=reinhardt, 2=filmic, 3=aces
fogLightColorNoFog light color {r,g,b,a}
glowIntensityNoGlow intensity
ssaoIntensityNoSSAO intensity
backgroundModeNo0=clear, 1=custom_color, 2=sky, 3=canvas
backgroundColorNoBackground color {r,g,b,a}
ambientLightColorNoAmbient light color {r,g,b,a}
ambientLightEnergyNoAmbient light energy
Behavior2/5

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

Annotations are minimal (only title), so the description carries full burden. It does not disclose side effects such as whether changes are immediate, require a scene reload, or affect other rendering settings. No warnings about performance or dependencies.

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?

The description is extremely concise (8 words) with no wasted text. It is front-loaded and clear, even if minimal.

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 has 19 parameters, no output schema, and no behavioral details, the description is insufficient. It fails to provide context on typical usage, defaults, or return values for 'get' actions.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter. It does not explain default values or how parameters interact.

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 clearly states the tool gets or sets environment and post-processing settings, which is a specific verb-resource combination. However, it does not differentiate from siblings like game_3d_effects or game_render_settings that may have overlapping functionality.

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 is provided on when to use 'get' vs 'set' or when to prefer this tool over alternatives. The description lacks context for appropriate usage scenarios.

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/Fulviuus/godot-mcp'

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