Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

setup_physics_body

Add a physics body node such as RigidBody3D, CharacterBody3D, or StaticBody3D to a Godot scene and specify its name and parent path.

Instructions

Add a physics body node (RigidBody3D, CharacterBody3D, StaticBody3D, etc.) to the scene.

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": {
      "body_type": "<body_type>"
    },
    "name": "setup_physics_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNode name
body_typeYesPhysics body class name
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 provided, so the description carries the full behavioral burden. It reveals nothing beyond 'adds a node' — not where the node is placed by default, whether the scene must be saved/refreshed, what happens if parent_path is omitted, or whether the operation is reversible.

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 wasted words; the examples of body types are the highest-value part and come immediately. It is efficient but borders on under-specified rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter additive tool with no output schema, a one-line description is close to proportionate, and the parenthetical examples help. Still, with zero annotations the description should at least say how the parent is chosen and what the tool returns (node path? node itself?).

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 name, body_type, and parent_path. The description adds marginal value by giving example values for body_type, but says nothing about parent_path resolution or default node naming.

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 (Add) and resource (physics body node) and enumerates concrete class names (RigidBody3D, CharacterBody3D, StaticBody3D), so an agent knows exactly what gets created. It doesn't explicitly name a contrasting sibling such as setup_collision or add_node, so it falls short of full sibling differentiation.

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 over setup_collision, add_node, or add_raycast, and no prerequisites are stated. The only implied usage is 'when you need a physics body in the scene', which the agent must infer.

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