Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_trigger_box_extent

DestructiveIdempotent

Resize a TriggerBox in Unreal Editor by setting its box collision half-extents and refreshing overlaps; marks the level dirty without saving.

Instructions

Resize a TriggerBox in the editor world by setting the unscaled half-extent of its box collision component and updating its overlaps; the level is marked dirty, not saved. Returns previous_extent, new_extent and changed. Each extent must be greater than 0.

Returns: { actor_name, component_name, previous_extent: {x, y, z}, new_extent: {x, y, z}, changed }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
extent_xYesHalf-extent along local X in cm, greater than 0; the box is twice as long.
extent_yYesHalf-extent along local Y in cm, greater than 0.
extent_zYesHalf-extent along local Z in cm, greater than 0.
actor_nameYesObject name of the TriggerBox actor in the editor world; its editor label is not matched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • changedInput schema / properties / actor_name / description
      Previous value: -"TriggerBox actor name (required)"New value: +"Object name of the TriggerBox actor in the editor world; its editor label is not matched."
    • changedInput schema / properties / extent_x / description
      Previous value: -"Box half-extent X (required, > 0)"New value: +"Half-extent along local X in cm, greater than 0; the box is twice as long."
    • changedInput schema / properties / extent_y / description
      Previous value: -"Box half-extent Y (required, > 0)"New value: +"Half-extent along local Y in cm, greater than 0."
    • changedInput schema / properties / extent_z / description
      Previous value: -"Box half-extent Z (required, > 0)"New value: +"Half-extent along local Z in cm, greater than 0."
  2. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With annotations present (destructive, idempotent, not read-only), the description adds valuable behavioral context beyond them: the level is 'marked dirty, not saved', overlaps are updated as a side effect, and the mutation returns previous/new extent plus a changed flag. Missing auth/permission notes but otherwise substantive.

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?

The description is front-loaded with the core operation and efficient. Mild redundancy exists between the inline 'Returns previous_extent, new_extent and changed' sentence and the fully expanded Returns block, but it stays tight.

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 documents the return shape (actor_name, component_name, previous_extent, new_extent, changed) and the dirty-not-saved persistence behavior. Complete enough for a single-purpose editor mutation.

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 schema already documents all four parameters (extent axes and actor_name). The description adds only marginal clarification ('unscaled', 'greater than 0'), so the baseline 3 applies.

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?

The description states a specific verb and resource ('resize a TriggerBox... by setting the unscaled half-extent of its box collision component') and clarifies the mechanism (updating overlaps). This clearly distinguishes it from sibling tools like set_trigger_sphere_radius or set_trigger_events.

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 context is implied ('in the editor world'), but there is no explicit when-to-use or when-not-to-use routing versus siblings such as remove_trigger_box or set_trigger_sphere_radius. The scope is clear enough to act, but no alternative is named.

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