Skip to main content
Glama

unreal_get_physics_info

Retrieves physics data for a selected Unreal Engine actor, helping you inspect collision, mass, and body settings for debugging or gameplay tuning.

Instructions

Get physics info for an actor.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does almost nothing with it: it does not say whether the call is read-only in effect, what fields the physics info comprises, or whether it fails for actors without a physics body. The presence of an output schema excuses explaining return values, but not the call semantics.

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

Conciseness3/5

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

A single front-loaded sentence with no filler, so nothing is wasted. The problem is under-specification rather than verbosity; the sentence is short but does not earn its place as an invocation guide.

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?

The tool is simple — one opaque parameter and one read operation — and an output schema exists to describe the payload, which limits what the description must cover. Still missing is any identification of the expected "params" content, which is the main risk of a misinvocation.

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 named "params" with 0% schema description coverage and no type information, and the description offers no clue what it should contain — presumably an actor identifier, but that is inferred from the phrase "for an actor" rather than stated. The definition leaves the only input effectively undocumented.

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 names a verb ("Get") and resource ("physics info") plus a scope ("for an actor"), which is more than a tautology. However, "physics info" is undefined and is not distinguished from near-siblings such as unreal_get_physics_settings or unreal_get_collision_info, so an agent cannot tell which to call.

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 exclusion of alternatives, and no mention of prerequisites such as needing an actor reference. The agent must guess that this is the read-side counterpart to unreal_set_physics_enabled / unreal_set_simulate_physics.

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