Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_physics_state

Retrieve a physics body’s velocity, angular velocity, and contact data for a node in the running Godot game to inspect or debug its current motion state.

Instructions

Get physics body state (velocity, angular velocity, contacts) for a node in the running game.

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

Input Schema

NameRequiredDescriptionDefault
node_pathYesNode path of the physics body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; using 'Get' plus enumerated return fields makes clear this is a non-mutating read. It does not state what happens if the node has no physics body, whether it errors or returns empty, or any cost/latency considerations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with no filler; the key qualifier (running game) and the returned fields are all stated up front.

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

Completeness4/5

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

For a one-parameter read tool with no output schema, listing the returned fields compensates well for the missing output schema. It falls short only on edge-case behavior (node without a physics body, editor vs running game failure modes).

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% for the single node_path parameter, so the baseline is 3. The description adds only that the node identifies a physics body in the running game, which is marginal meaning beyond the schema's 'Node path of the physics body'.

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?

A specific verb (Get) plus resource (physics body state) and it enumerates the returned fields (velocity, angular velocity, contacts) scoped to a node in the running game. It is clearly distinguishable from mutation-oriented siblings like setup_physics_body, though it does not name any sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'in the running game' implies a prerequisite (the game must be running) and thus separates it from editor-state tools, but there is no explicit when-to-use/when-not guidance and no named alternative such as get_game_node_properties for non-physics data.

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