Skip to main content
Glama

set_box_slot_properties

DestructiveIdempotent

Configure box-slot alignment, padding, and fill size for a widget child of HorizontalBox, VerticalBox, Overlay, Border, SizeBox, or ScrollBox in Unreal Engine.

Instructions

Configure a widget's box-family slot layout (alignment/padding/size). Applies when the widget is parented under a HorizontalBox/VerticalBox/Overlay/Border/SizeBox/ScrollBox; dispatches by the concrete slot type. Size only applies to Horizontal/Vertical/ScrollBox slots -- on the others it is returned as an honest note. For a CanvasPanel child use set_widget_slot_properties; for a GridPanel child use set_grid_slot_properties.

Returns: { widget_bp_path: string, widget_name: string, slot_type: string, settings_applied: object, applied_count: int, notes: [string], saved: bool, save_error: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoOptional. This command is REFUSED while a Play-in-Editor session is running: it either compiles a Blueprint (the reinstancer can retain a world, and CheckForWorldGCLeaks is Fatal -- it KILLS the editor) or writes to disk (Editor.AllowSavingAssetsDuringPIE=0 makes the engine refuse the write, so it would report success without writing a byte). Stop PIE and retry instead; force=true runs it anyway, at your own risk.
paddingNoOptional [Left, Top, Right, Bottom] floats (also accepts [uniform] or [horizontal, vertical]).
size_ruleNoOptional Fill | Auto (Horizontal/Vertical/ScrollBox slots only).
size_valueNoOptional float fill weight (used with size_rule = Fill; default 1.0).
widget_nameYesname of the child widget whose box slot to edit
blueprint_nameNoAlias of `widget_bp_path` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `widget_bp_path`.
widget_bp_pathNo/Game path of the Widget Blueprint asset
vertical_alignmentNoOptional alignment: Fill | Top | Center | Bottom
horizontal_alignmentNoOptional alignment: Fill | Left | Center | Right

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructive=true and idempotent=true. The description adds real context beyond that: dispatch-by-concrete-slot-type, the size limitation that only applies to Horizontal/Vertical/ScrollBox (returned as a note elsewhere), and the return object shape. It does not state the PIE-refusal risk beyond what the schema's force param carries, but the schema covers that.

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 purpose, then routing alternatives, then the Returns block. No filler; every sentence earns its place.

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 9-param mutation tool with an inline Returns listing, the description covers scope, routing, conditional applicability, and the return shape. Category-specific caveats and the PIE refusal live in the schema, which is reasonable.

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 description coverage is 100%, so baseline 3. The description adds meaning beyond the schema by clarifying that size params only take effect on certain slot types, which contextualizes size_rule/size_value beyond their per-param docs.

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 (Configure) and resource (a widget's box-family slot layout), and explicitly distinguishes itself from set_widget_slot_properties (CanvasPanel) and set_grid_slot_properties (GridPanel). An agent can route correctly without opening any 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 the parent-widget conditions under which it applies (HorizontalBox/VerticalBox/Overlay/Border/SizeBox/ScrollBox) and names the two alternative tools with their selection conditions. Explicit when-to-use and alternatives.

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