Skip to main content
Glama

unreal_set_simulate_physics

Toggle physics simulation on an actor to enable or disable gravity, collisions, and rigid-body movement directly in an Unreal Engine 5 project.

Instructions

Toggle simulate physics.

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_simulate_physics"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 burden, and it discloses almost nothing. "Toggle" implies state reversal and possible side effects (simulation resuming, state persisting, required editor context), but none of that is stated, nor are permissions or failure modes.

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

Conciseness2/5

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

One terse fragment is technically free of waste but is under-specified rather than concise. Brevity here comes at the cost of the targeting and parameter information an agent needs before invoking.

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?

The tool mutates simulation state, has no annotations, and has a completely undocumented parameter object, so the description needed to do real work. An output schema exists and need not be explained, but the missing parameter and target details leave the definition incomplete for safe invocation.

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

Parameters1/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 opaque, untyped "params" object. The description adds no information about the parameter's shape or contents, so an agent has no way to know what to pass.

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?

"Toggle simulate physics" names a verb and a resource, so the operation is guessable. But it never says what is being toggled (which actor/component) or how this differs from the near-identical sibling unreal_set_physics_enabled, leaving a real risk of picking the wrong tool.

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 at all — no prerequisites, no mention of when to prefer this over unreal_set_physics_enabled (which likely sets an explicit state rather than flipping it), and no context about editor vs. runtime state.

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