Skip to main content
Glama

unreal_set_gravity

Enable or disable gravity and set its scale in Unreal Engine 5 to control physics behavior in a project.

Instructions

Set gravity enabled/scale.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 behavioral burden, yet it only restates that gravity can be toggled or scaled. It says nothing about required permissions, whether the change is global or per-actor, whether it persists, or whether existing gravity settings are overwritten.

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?

The single fragment is short but under-specified rather than concise: it omits the subject of the operation and any context. There is no wasted wording, but there is also almost no content to front-load.

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?

A mutation tool with no annotations, an opaque nested "params" object, and no description of what changes or fails would need substantially more detail. The existence of an output schema reduces the need to explain return values, but the input side remains undocumented.

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?

There is one required parameter literally named "params" with 0% schema description coverage, and the description does not document its structure or accepted keys. The phrase "enabled/scale" hints that the payload contains a boolean and a numeric factor, but the agent is left guessing at field names and value ranges.

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?

"Set gravity enabled/scale" names a specific resource (gravity) and the two aspects being modified, which separates it from unrelated siblings like unreal_set_actor_scale or unreal_set_physics_enabled. However, it never states the scope of the gravity being changed (world/environment settings vs. a specific actor or volume), so an agent cannot tell exactly what object it operates on.

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?

The description gives no when-to-use guidance, no prerequisites, and no indication of how it differs in practice from nearby tools such as unreal_set_environment_settings or unreal_set_physics_enabled. Any routing decision must be inferred from the name alone.

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