Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_geometry_collection_damage

DestructiveIdempotent

Configure the damage model and per-level damage thresholds for a UGeometryCollection asset and save changes to disk. Returns saved status and damage info.

Instructions

Set the damage model and/or the per-level damage thresholds of a UGeometryCollection asset in an undo transaction, then save it. Only the fields given change; damage_thresholds overwrites the whole threshold list, skipping entries that are not numbers. Succeeds only when the package reaches disk; a failed save leaves the change in memory only (saved false, save_error). The reply reads back damage_model ("Threshold", "MaterialStrength" or "Unknown") and num_thresholds; get_geometry_collection_info shows them later. Mass: set_geometry_collection_mass; clustering: set_gc_connection_settings.

Returns: { geometry_collection_path: string, damage_model: string, num_thresholds: int, success: bool, saved: bool, save_error: string? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
damage_modelNoThreshold (alias UserDefined) or Simple (alias Material, the material-strength model), case-insensitive; any other text means Threshold, and leaving it out keeps the current model.
damage_thresholdsNoOptional array of per-level damage threshold floats
geometry_collection_pathYesFull asset path to the UGeometryCollection

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / damage_model / description
      Previous value: -"Threshold or Simple, default Threshold"New value: +"Threshold (alias UserDefined) or Simple (alias Material, the material-strength model), case-insensitive; any other text means Threshold, and leaving it out keeps the current model."
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond annotations: undo-transaction wrapping, save-to-disk success semantics, and the failure state (change stays in memory, saved=false with save_error). It also discloses the destructive overwrite behavior of damage_thresholds and skipping of non-number entries, which annotations only summarize as destructiveHint=true.

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-loads the core action and keeps each sentence informative (overwrite semantics, save behavior, return values, sibling routing). Slightly dense but every clause earns its place with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description compensates with a Returns block documenting the full response shape and includes failure semantics for a mutation tool. Nothing an agent needs to invoke and interpret it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: damage_thresholds overwrites the entire list rather than merging, and non-numeric entries are skipped. It also confirms the read-back damage_model values. This goes beyond the schema's brief parameter text.

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 and resource ('Set the damage model and/or the per-level damage thresholds of a UGeometryCollection asset') and distinguishes itself from adjacent siblings by naming mass and clustering tools. An agent can tell exactly what this does 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 Guidelines4/5

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

Gives clear context ('Only the fields given change') and routes to siblings for other concerns (set_geometry_collection_mass, set_gc_connection_settings), and points to get_geometry_collection_info for later verification. It stops short of explicit when-not guidance, so it's clear but not exhaustive.

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