Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

cluster_geometry_collection

Destructive

Clusters all transforms in a UGeometryCollection into connected groups at a target site count, scaling via Small/Medium/Large, then saves the asset.

Instructions

Runs auto-clustering on all transforms of a UGeometryCollection asset, targeting site_count clusters ("Small" doubles it, "Large" halves it, any other method keeps it) with connectivity enforced, then saves it. Returns the cluster count used and the transform counts before and after; the call fails when no cluster was added (a collection that is not fractured into several pieces has nothing to group) or when the save fails.

Returns: { geometry_collection_path: string, cluster_size_method: string, site_count: int, num_transforms_before: int, num_transforms_after: int, success: bool, saved: bool, save_error: string? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_countNoTarget cluster count before cluster_size_method scales it, minimum 1, default 10
cluster_size_methodNoSmall, Medium, or Large, default Medium
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 / site_count / description
      Previous value: -"Base site count used by the size method, default 10"New value: +"Target cluster count before cluster_size_method scales it, minimum 1, default 10"
  2. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description goes further by disclosing the two failure modes (no cluster added, save failure), the automatic save, and how cluster_size_method scales site_count — real context beyond the structured fields. It stops short of stating reversibility of the clustering.

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, then behavior and failure modes. The trailing Returns block duplicates part of the prose but is compact and structurally useful given there is no output schema. Minor density, no real waste.

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 supplies the full return shape and both error conditions, and the annotations carry the safety profile. An agent has everything needed to invoke and interpret the call.

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 the baseline is 3, but the description adds meaning the schema does not: the interaction between site_count and cluster_size_method ("Small" doubles, "Large" halves, any other keeps). That is genuine added semantics over the per-parameter descriptions.

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 — auto-clustering of all transforms on a UGeometryCollection asset — plus the scoping effect of site_count and the save step. An agent can distinguish it from siblings like fracture_geometry_collection, create_geometry_collection, or get_geometry_collection_info without opening a 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?

Usage is implied through the failure condition (a collection not fractured into several pieces has nothing to group), which signals a prerequisite, but there is no explicit when-to-use vs when-not guidance and no sibling is named as an alternative. Adequate but with a clear gap.

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