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

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

game_physics_3d

Run Area3D overlap checks, point and shape intersection tests, and ray casts to detect collisions and query 3D space in Godot scenes.

Instructions

Area3D queries and point/shape intersection tests

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "game_physics_3d"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoRay end {x,y,z}
fromNoRay/point origin {x,y,z}
actionYesAction: overlap, point_query, shape_query, ray
nodePathNoArea3D/node path (for overlap)
collisionMaskNoCollision mask bitmask

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?

No annotations are provided, so the description carries the full burden. 'Queries and intersection tests' weakly implies read-only behavior, but it doesn't state whether there are side effects, what results are returned, or any scene/Area3D requirements. A read-only hint is not explicitly given.

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?

The description is a single front-loaded phrase with no filler or repetition of the parameter schema. It is too terse to carry full behavioral weight, but as a conciseness/structure measure there is no waste.

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 multi-action tool with 5 parameters, no output schema, and no annotations, the description is too sparse. It does not explain each action's expected parameter usage, return values, or how shape_query differs from point_query/ray, so an agent would likely need to open other tools or infer behavior.

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 applies. The description adds only the context that these are Area3D/intersection operations; it doesn't elaborate on how 'from', 'to', 'nodePath', or 'collisionMask' are used per action, but the schema already describes each property.

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 names a specific resource (Area3D) and operations (point/shape intersection tests), and the schema's action values clarify the included modes (overlap, point_query, shape_query, ray). However, it doesn't explicitly contrast with siblings like game_raycast or game_physics_2d, leaving some differentiation to inference.

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 choose this tool over game_raycast or other physics/query siblings, nor any exclusions or prerequisites. The only usage signal is the schema's action list, which the agent must interpret on its own.

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