Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_collision

Add a CollisionShape2D or CollisionShape3D with a specified shape to a parent physics body node, enabling collision setup for Godot scenes.

Instructions

Add a CollisionShape3D/2D with a given shape to a node.

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": {
      "node_path": "<node_path>"
    },
    "name": "setup_collision"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesParent physics body node path
propertiesNoShape property overrides
shape_typeNoShape class (BoxShape3D, SphereShape3D, etc.)

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?

With no annotations supplied, the description carries the full burden of behavioral disclosure. It does not say whether a new child node is created versus an existing shape being altered, whether an existing collision shape is replaced, whether shape_type defaults are applied, or what the tool returns on success or failure.

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 or redundancy. It is efficient, though its brevity borders on under-specification for a mutation-style tool.

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 that adds a node to the scene graph, with a nested override object and no annotations or output schema to fall back on, the definition should explain creation versus mutation semantics and the risk of duplicate shapes. The one-line description leaves those behavioral questions unanswered.

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 all three parameters including the nested properties object are already documented structurally. The description adds only the generic notion of "a given shape" and a target node, contributing little meaning beyond the schema; 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?

The description states a specific verb ("Add") and resource ("CollisionShape3D/2D") and indicates the target node, so an agent can identify the operation. It stops short of distinguishing itself explicitly from setup_physics_body or add_mesh_instance siblings, and "to a node" is looser than the schema's more precise "Parent physics body node path".

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 prerequisites (e.g. that the parent should be a physics body), and no mention of alternatives such as setup_physics_body. The agent must infer the applicable context entirely from the name and schema.

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