Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_physical_material_properties

DestructiveIdempotent

Set friction, restitution, density, and other surface properties on a UPhysicalMaterial asset in Unreal Engine. Updates only specified fields and verifies changes.

Instructions

Load a UPhysicalMaterial, set surface/object properties, save, and read back (read-modify-write; only provided fields change; idempotent set-to-fixed-value).

Returns: { physical_material_path: string, friction: number, static_friction: number, restitution: number, density: number, friction_combine_mode: string, override_friction_combine_mode: bool, restitution_combine_mode: string, override_restitution_combine_mode: bool, surface_type: string, raise_mass_to_power: number, sleep_linear_velocity_threshold: number, sleep_angular_velocity_threshold: number, friction_applied: bool, static_friction_applied: bool, restitution_applied: bool, density_applied: bool, friction_combine_mode_applied: bool, restitution_combine_mode_applied: bool, surface_type_applied: bool, raise_mass_to_power_applied: bool, sleep_linear_velocity_threshold_applied: bool, sleep_angular_velocity_threshold_applied: bool, updated: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
densityNoOptional new Density value (g/cm^3, >= 0)
frictionNoOptional new (kinetic) Friction value (>= 0)
restitutionNoOptional new Restitution value (clamped to [0,1])
surface_typeNoOptional EPhysicalSurface by reflected name (e.g. 'SurfaceType_Default','SurfaceType1') or numeric value
static_frictionNoOptional new StaticFriction value (>= 0)
raise_mass_to_powerNoOptional RaiseMassToPower (clamped to [0.1,1])
friction_combine_modeNoOptional Average|Min|Multiply|Max (sets bOverrideFrictionCombineMode true)
physical_material_pathYes/Game path to the physical material asset.
restitution_combine_modeNoOptional Average|Min|Multiply|Max (sets bOverrideRestitutionCombineMode true)
sleep_linear_velocity_thresholdNoOptional SleepLinearVelocityThreshold (>= 0)
sleep_angular_velocity_thresholdNoOptional SleepAngularVelocityThreshold (>= 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, so the safety profile is covered. The description adds genuine context beyond them: the load/save/read-back workflow, that only supplied fields are mutated, and that unspecified settings are left alone. It stops short of stating permission requirements or failure behavior for an invalid path.

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?

The operative sentence is front-loaded and efficient, but the trailing inline dump of ~22 return fields is a long unformatted blob that mostly repeats parameter names with _applied suffixes. With no output schema this has some value, yet it is not proportionate to the rest of the description.

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 an 11-parameter mutation tool with no output schema, the description covers both what is mutated (partial, only provided fields) and what comes back (the applied-flags payload), which compensates for the missing output schema. Gaps remain around error/validation behavior and preconditions, so it is not fully complete.

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% (units, clamps, enum-like modes are all in the schema), so the baseline is 3. The description adds no parameter syntax or defaults beyond what the schema already documents; its return-field list merely echoes the same names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb chain (load → set → save → read back) on a named resource (UPhysicalMaterial), and the parenthetical read-modify-write / only-provided-fields clause makes the scope unambiguous. An agent can distinguish this from sibling setters like set_physics_body_properties without opening the schema.

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?

The read-modify-write and idempotent framing implies when to reach for this tool (partial updates to an existing physical material asset), but it never names when NOT to use it, nor routes to siblings such as create_physical_material, set_actor_physical_material, or set_material_physical_material. Usage is inferable but not explicit.

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