Better Godot MCP

Overview Schema Source Related Servers Discussions Admin

physics

Configure Godot physics layers, collisions, and body properties to manage interactions and gravity settings directly from your MCP workflow.

Instructions

Physics config. Actions: layers|collision_setup|body_config|set_layer_name. Use help tool for full docs.

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": "physics"
  }
}

Input Schema

Name	Required	Description
`mass`	No	Mass (for body_config)
`name`	No	Node name
`action`	Yes	Action to perform
`dimension`	No	2d or 3d (for set_layer_name)
`scene_path`	No	Path to scene file
`layer_number`	No	Layer number (for set_layer_name)
`project_path`	No	Path to Godot project directory
`gravity_scale`	No	Gravity scale (for body_config)
`collision_mask`	No	Collision mask bitmask
`collision_layer`	No	Collision layer bitmask

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.20.0Jul 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "type": "object"
+}

First observedv1.5.1Mar 12, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context such as side effects, permissions, or whether actions modify state. With no compensation from the description, the agent lacks understanding of potential impacts.

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?

The description is very short, but this brevity sacrifices clarity. It front-loads 'Physics config' and lists actions, which is somewhat structured, but the utility of the description is limited. Every sentence is used, but the content is insufficient for an agent to use the tool effectively.

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 the high parameter count (10) and the presence of an output schema, the description is severely lacking. It does not explain the behavior of each action, parameter dependencies, or expected outputs. The tool is complex, but the description provides almost no contextual completeness.

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 coverage is 100%, with each parameter having a brief description. The description adds no additional meaning beyond listing action names; it does not explain which parameters apply to which actions. The schema already provides basic context, so the description offers minimal extra value.

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 states 'Physics config' and lists four actions, giving a general sense of the tool's purpose. However, it is vague and does not clearly specify what each action does or how the tool is used. The phrase 'Use help tool for full docs' suggests incompleteness.

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 explicit guidance on when to use this tool vs alternatives. The description does not mention any prerequisites, context, or scenarios where physics should be chosen over sibling tools like animation or navigation. The instruction to use the help tool indicates the description is insufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server