Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_physics_body_advanced_properties

DestructiveIdempotent

Update advanced physics body properties—damping, mass scale, inertia, center of mass, gravity, and scale-based mass—on a chosen UPhysicsAsset body, then save the asset.

Instructions

Writes only the given advanced FBodyInstance fields (damping, mass scale, inertia scale, COM nudge, gravity, mass update on scale) of one body of a UPhysicsAsset, chosen by body_index or bone_name, and saves it. Fails when no field is given. Returns the authored values read back, applied_count, saved.

Returns: { physics_asset_path: string, body_index: int, bone_name: string, linear_damping: number, angular_damping: number, mass_scale: number, inertia_tensor_scale: [number], com_nudge: [number], enable_gravity: bool, update_mass_when_scale_changes: bool, applied_count: int, updated: bool, saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bone_nameNoBone name to resolve the body (alternative to body_index).
com_nudgeNo[x,y,z] center-of-mass offset.
body_indexNoIndex of the body in the asset; wins over bone_name when both are given
mass_scaleNoPer-instance mass multiplier (>= 0.001).
enable_gravityNoWhether the body is affected by gravity.
linear_dampingNoDrag that slows linear movement (FBodyInstance LinearDamping, unitless, engine default 0.01); omit to keep the current value
angular_dampingNoDrag that slows rotation (FBodyInstance AngularDamping, unitless, engine default 0); omit to keep the current value
physics_asset_pathYes/Game path to the UPhysicsAsset.
inertia_tensor_scaleNo[x,y,z] inertia scale.
update_mass_when_scale_changesNoRecompute mass on scale change.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.2.0
    • changedInput schema / properties / angular_damping / description
      Previous value: -"Angular drag."New value: +"Drag that slows rotation (FBodyInstance AngularDamping, unitless, engine default 0); omit to keep the current value"
    • changedInput schema / properties / body_index / description
      Previous value: -"Explicit body index (or use bone_name)."New value: +"Index of the body in the asset; wins over bone_name when both are given"
    • changedInput schema / properties / linear_damping / description
      Previous value: -"Linear drag."New value: +"Drag that slows linear movement (FBodyInstance LinearDamping, unitless, engine default 0.01); omit to keep the current value"
  2. First observedv1.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Against annotations that already declare destructive=true, idempotent=true and readOnly=false, the description adds real behavioral detail: only the provided fields are written (patch semantics, other fields untouched), the change is saved, it errors when no field is supplied, and the authored values are read back. It does not restate the safety hints, adding genuine context.

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 prose is front-loaded and dense with no filler, and the trailing "Returns" block is justified because no output schema exists. The inline return signature is bulky but each line earns its place for an agent consuming the result.

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?

For a mutation tool with no output schema, the description covers the key gaps: partial-write semantics, the save side effect, the no-field failure mode, body targeting, and the full return shape. An agent has enough to call and interpret it, with only sibling routing left unaddressed.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all ten parameters including defaults and units. The description names the editable fields and the body-resolution rule but adds no format or precedence detail beyond what the schema provides; baseline 3 applies.

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?

States a specific verb ("Writes") and resource ("advanced FBodyInstance fields ... of one body of a UPhysicsAsset"), and enumerates exactly which fields it touches (damping, mass scale, inertia scale, COM nudge, gravity, mass update on scale). This meaningfully separates it from the generic sibling set_physics_body_properties, though that sibling is never named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a valid usage constraint ("Fails when no field is given") and how the body is targeted ("by body_index or bone_name"), which implies partial-update usage. However, it never states when to prefer this over the plain set_physics_body_properties, leaving the choice between the two advanced/basic setters to inference.

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