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

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_environment

Get or set Godot environment and post-processing settings, including fog, glow, SSAO, SSR, tonemapping, background, and ambient lighting.

Instructions

Get or set environment and post-processing settings

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "game_environment"
  }
}

Input 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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, but 'Get or set...' only discloses that the tool has read and write modes. It does not reveal that 'set' is the default action, what 'get' returns, whether partial updates merge or reset unmentioned settings, or any error/validation behavior.

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?

A single front-loaded sentence with no filler; it wastes nothing. It is efficient but so terse that it sacrifices context that a 19-parameter tool needs, though that tradeoff belongs more to completeness than to structure.

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 19 parameters, no output schema, and no annotations, the description is too thin. It omits the default action behavior, return shape for 'get', how settings are applied when only a subset is provided, and relationship to the running game environment. An agent has enough to guess the tool's domain but not enough to call 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?

The input schema covers all 19 parameters with individual descriptions, so the baseline is 3. The tool description adds no parameter-level meaning, and it does not compensate for missing ranges, units, or mode-specific interactions, but it does not need to reiterate 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?

The description uses a clear verb ('Get or set') and names a concrete resource ('environment and post-processing settings'), which the input schema confirms (fog, bloom, SSAO, tonemapping, backgrounds). It is not vague, but it does not differentiate from closely related siblings like game_render_settings or game_3d_effects, so it falls just short of a 5.

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 mention of alternatives, and no exclusions. An agent must infer from the name and schema when game_environment is appropriate versus game_render_settings, game_3d_effects, game_world_settings, or game_sky. The sentence states capability but not selection criteria.

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