Skip to main content
Glama
Sign In
Unreal Engine MCP

Unreal Engine MCP

by FFZackFair92
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ue_set_component_physics

Configure physics and collision options for a component on an actor in Unreal Engine: toggle simulation, set collision enabled state, and apply a collision profile.

Instructions

Fisica e collisione di un componente (StaticMesh/Skeletal/Primitive).

Args: actor: etichetta dell'attore nell'Outliner. component: nome o classe del componente (es. "StaticMeshComponent"). simulate_physics: attiva/disattiva la simulazione fisica. collision_enabled: "NoCollision" | "QueryOnly" | "PhysicsOnly" | "QueryAndPhysics" | "QueryAndProbe" | "ProbeOnly" (case/underscore insensitive, es. va bene anche "query_and_physics"). collision_profile: nome profilo collisione (es. "PhysicsActor", "BlockAll").

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": {
      "actor": "<actor>",
      "component": "<component>"
    },
    "name": "ue_set_component_physics"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYes
componentYes
simulate_physicsNo
collision_enabledNo
collision_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.10.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description must disclose side effects and preconditions. It does not mention what happens when physics simulation is toggled, whether changes are persistent, or if any component type restrictions exist beyond the examples. This is a significant gap for a mutation tool.

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?

The description is compact and well-organized as a parameter list. It includes an intro line and detailed args with no redundant text. The intro could be a verb phrase, but overall it is efficient and scannable.

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 description is essentially a parameter list without an overall explanation of the operation's effect, when to use it, or any side effects. Given that annotations and output schema are absent, this is insufficient for a complete understanding of the tool's context and behavior.

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

Parameters5/5

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

The description provides rich meanings for all five parameters, including allowed values, case-insensitivity, and examples (e.g., collision_enabled values and collision_profile names). This fully compensates for the schema's 0% description coverage.

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 is a noun phrase ('Fisica e collisione di un componente') that names the topic but lacks an explicit verb such as 'set' or 'configure'. It identifies the resource (component) and scope (StaticMesh/Skeletal/Primitive), but relies on the tool name to convey the action, making it a vague standalone purpose.

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 guidance is provided about when to use this tool versus alternatives like ue_component_physics_info. There are no prerequisites, exclusions, or conditions described. The description is purely parameter documentation.

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