Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_geometry_collection_mass

DestructiveIdempotent

Updates specified mass, density, minimum mass clamp, or physics-material density settings on a UGeometryCollection asset and saves them undoably.

Instructions

Writes the mass settings of a UGeometryCollection asset (mass, mass_as_density, minimum_mass_clamp, density_from_physics_material), only for the fields given, then saves it; undoable. Returns the four values as stored, success, saved; fails when the save fails. Read them back with get_geometry_collection_info.

Returns: { geometry_collection_path: string, mass: float, mass_as_density: bool, minimum_mass_clamp: float, density_from_physics_material: bool, success: bool, saved: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
massNoOptional total mass (kg), or density (kg/m^3) when mass_as_density is true
mass_as_densityNoOptional, interpret 'mass' as a density in kg/m^3, default unchanged
minimum_mass_clampNoOptional smallest allowable mass, default unchanged
geometry_collection_pathYesFull asset path to the UGeometryCollection
density_from_physics_materialNoOptional, derive density from the physics material, default unchanged

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations cover the safety profile (destructive, idempotent, not read-only). The description adds real context beyond them: it saves the asset, is undoable, returns the stored values, and fails when the save fails. Doesn't detail what exactly is destroyed, but a setter's scope is well understood here.

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?

Front-loaded with the core action and scope, followed by outcome and read-back guidance. Slight redundancy in the trailing Returns block re-listing fields already named, but overall tight and useful.

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?

No output schema exists, but the description supplies the return shape and failure condition, and covers the save/undo behavior an agent needs. Complete enough for a field-scoped setter.

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 baseline is 3. The description reinforces the four fields and the partial-write behavior, but adds no format or syntax detail beyond what the schema already states ('default unchanged').

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 (writes mass settings) and resource (UGeometryCollection asset), and enumerates the exact fields it touches. An agent can distinguish this from get_geometry_collection_info, which it explicitly names for read-back.

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

Usage Guidelines4/5

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

Clarifies partial-update semantics ('only for the fields given') and routes read-back to get_geometry_collection_info. No explicit when-not-use or prerequisites, but the usage context is clear.

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