Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_raycast

Add RayCast2D or RayCast3D nodes to Godot scenes to detect collisions, measure distances, and implement line-of-sight mechanics in game development.

Instructions

Add RayCast2D or RayCast3D. (Compatibility tool)

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
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for behavioral disclosure but only offers the unexplained 'compatibility' label. It does not state whether the tool creates, modifies, or references existing nodes, nor does it explain side effects or return values.

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?

While the description is brief and front-loaded, its extreme brevity is inappropriate given the lack of schema documentation and annotations. The '(Compatibility tool)' aside consumes space without conveying actionable information.

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 zero schema descriptions, no annotations, and the presence of cryptic parameters (timeoutMs, autoConnect), the description is insufficient. It does not compensate for the missing structured metadata needed to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage for timeoutMs and autoConnect, yet the description provides no semantic context for these parameters. It also fails to document what RayCast-specific properties (beyond the two generic ones shown) are accepted via additionalProperties.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the specific node types (RayCast2D/3D) but the '(Compatibility tool)' parenthetical is cryptic and unexplained, muddying the purpose. It also fails to clarify when to use this specialized tool versus the generic add_node sibling.

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 prefer this tool over add_node or other alternatives. The 'compatibility' label suggests a specific use case but offers no criteria for selection.

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