Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

apply_uniform_remesh

Destructive

Remesh a DynamicMeshActor's live mesh into evenly sized triangles using either a target edge length or triangle count; applies in the editor and reports resulting geometry.

Instructions

Remesh the live dynamic mesh of a DynamicMeshActor in the editor world into evenly sized triangles, aiming at target_edge_length (cm) or target_tri_count: exactly one is required, else an error. The mesh changes in place inside an editor transaction and the actor's package is marked dirty, not saved. smoothing_type picks uniform, UV-preserving or mixed smoothing; an unknown value is an error. The reply echoes the settings the engine was given. remeshed is true when the triangle or vertex count changed. For variable density use apply_adaptive_remesh; to only reduce triangles, simplify_mesh.

Returns: { actor_name: string, target_edge_length: number, target_tri_count: int, preserve_sharp_edges: bool, smoothing_type: string, auto_compact: bool, target_type: string, triangle_count: int, triangle_count_before: int, vertex_count: int, remeshed: bool }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actor_nameYesLabel or name of the target DynamicMeshActor
auto_compactNoAuto-compact the index space after remesh on the shared RemeshOptions (default true).
smoothing_typeNoOne of 'uniform' | 'uv_preserving' | 'mixed' (default 'mixed'); maps to EGeometryScriptRemeshSmoothingType on the shared RemeshOptions.
target_tri_countNoApproximate target triangle count (sets TargetType=TriangleCount). Mutually exclusive with target_edge_length.
target_edge_lengthNoTarget uniform edge length in mesh units (sets TargetType=TargetEdgeLength). Mutually exclusive with target_tri_count; at least one is required.
preserve_sharp_edgesNoApproximate 'preserve sharp edges' by enabling bPreventNormalFlips on the shared RemeshOptions (default true; UE's FGeometryScriptUniformRemeshOptions has no explicit preserve-sharp flag, so the closest equivalent is the shared RemeshOptions.bPreventNormalFlips).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds real context: the mesh changes in place inside an editor transaction and the actor's package is marked dirty but not saved. It also defines the `remeshed` return flag semantics and the error behavior for bad smoothing_type values. Missing only permission/undo-reversibility specifics, but this is well beyond the annotation bar.

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

Conciseness5/5

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

Front-loaded with what the tool does, then constraints, then mutation behavior, then sibling routing — every sentence carries distinct information with no filler. Dense but well-ordered.

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?

For a destructive mesh-mutation tool with no output schema, the description still gives the return field list, the `remeshed` boolean meaning, the in-place/transaction/dirty semantics, and the alternatives. An agent has everything needed to call it correctly.

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 coverage is 100%, so the schema already documents all six parameters including the mutual exclusivity. The description mostly restates that constraint (adding an error consequence and a 'cm' unit alongside the schema's 'mesh units'), which is marginal value over the structured fields. Baseline 3 is appropriate when the schema carries the parameter load.

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 (Remesh) and resource (the live dynamic mesh of a DynamicMeshActor), plus the two targeting modes. It explicitly names the siblings it is not for — apply_adaptive_remesh and simplify_mesh — so an agent can separate it from the nearest alternatives without opening either schema.

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

Usage Guidelines5/5

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

Names alternatives with their selecting conditions ('For variable density use apply_adaptive_remesh; to only reduce triangles, simplify_mesh') and states the hard precondition that exactly one of target_edge_length/target_tri_count is required, else an error. Nothing is left 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