Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_reflection_probe

Adds a ReflectionProbe node to a specified parent in the Godot scene, with optional property overrides for configuring reflections.

Instructions

Add a ReflectionProbe node to the scene.

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": "setup_reflection_probe"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertiesNoReflectionProbe property overrides
parent_pathNoParent node path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says a node is added. It does not disclose whether the node is created at the scene root when parent_path is omitted, whether existing nodes are affected, what the call returns (node path/handle), or whether the operation is undoable.

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 zero padding, but its brevity comes at the cost of the missing behavioral detail rather than through efficient information density.

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 scene-mutating tool with no annotations and no output schema, the definition is too thin: the agent cannot tell what the call produces or what default behavior applies when the optional parameters are omitted. Only the bare purpose is conveyed.

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 both parameters (properties override object and parent_path) are already documented in the schema. The description adds no additional meaning about default placement or expected property keys, so the baseline of 3 applies.

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?

States a specific verb and resource ('Add a ReflectionProbe node to the scene'), which is enough for an agent to distinguish it from setup_lighting or setup_camera_3d by resource type. It stops short of explicitly contrasting with sibling setup_* tools, but the resource is unambiguous.

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 guidance on when to use this versus other setup_* tools or generic add_node, no stated prerequisites (e.g., an open scene, a valid parent), and no exclusions. The agent must infer usage entirely from the name and resource type.

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