Skip to main content
Glama

unreal_set_physics_enabled

Enable or disable physics simulation on an Unreal Engine actor or component to control collision response, gravity, and other physical forces.

Instructions

Enable/disable physics on an actor/component.

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": {
      "params": "<params>"
    },
    "name": "unreal_set_physics_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/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 behavioral burden and delivers very little. It does not say whether toggling physics resets velocities, whether the change is reversible or persists, whether it requires Play-In-Editor, or what the tool returns — all material for a mutation on a physics state.

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?

One short, front-loaded sentence with no wasted wording. It is terse rather than bloated, though the terseness comes at the cost of the missing detail flagged elsewhere.

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 write tool with zero annotation coverage, an opaque one-parameter object, and a live physics side effect, the definition is under-specified. The existence of an output schema relieves it of documenting return values, but the targeting and toggle semantics remain unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is an untyped 'params' object, so the schema explains nothing. The description only hints that the caller targets an 'actor/component' and toggles an enabled state; it never names the expected fields or their formats, so it does not compensate for the coverage gap.

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 pair (enable/disable) and resource (physics on an actor/component), which is more than a restatement of the name. It does not, however, distinguish this from the sibling 'unreal_set_simulate_physics', so an agent cannot tell from the text alone which of the two to pick.

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 mention of prerequisites (e.g. whether simulate-physics must already be on), and no reference to the obvious alternative 'unreal_set_simulate_physics'. The agent is left to infer the selection rule entirely.

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