Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

add_raycast

Add a RayCast2D or RayCast3D node to a Godot scene, specifying parent path, target position, and property overrides for AI-driven game development.

Instructions

Add a RayCast3D/2D 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": "add_raycast"
  }
}

Input Schema

NameRequiredDescriptionDefault
propertiesNoAdditional property overrides
parent_pathNoParent node path
target_positionNoTarget position vector

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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, and it discloses almost nothing: not whether the new node is selected or made current, what defaults are applied (e.g. ray length, collision mask), what happens if parent_path is invalid, or whether the operation requires an open scene. For a scene-mutating tool with zero annotation coverage this is a substantial gap.

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?

A single eleven-word sentence with no filler, front-loading the verb and resource well. However, it is under-specified rather than genuinely concise for a three-parameter scene mutation, so the efficiency comes at the cost of usefulness.

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?

With no annotations, no output schema, a nested properties override object, and all parameters optional, the description would need to explain defaults, return/error behavior, and editor-state prerequisites. It provides none of these, leaving an agent unable to predict the tool's side effects.

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 schema already documents properties, parent_path, and target_position with their nested x/y/z fields. The description adds no meaning beyond that — notably nothing about whether parent_path defaults to the scene root when omitted (0 required parameters). Baseline 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 plus resource ('Add a RayCast3D/2D node') and the destination ('to the scene'), which is enough to tell it apart from generic siblings like add_node or add_mesh_instance by the node type being created. It stops short of explicitly naming those siblings, so it is clear but not fully differentiated.

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 or when-not-to-use guidance, no reference to add_node as the generic alternative, and no statement of prerequisites or preconditions. The agent is left to infer entirely when this specialized node-adder should be preferred.

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