Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_chooser_column_default

DestructiveIdempotent

Set a UChooserTable column's default value before adding rows so appended rows inherit it; applies column-specific fields in one undoable, saved step.

Instructions

Set the DefaultRowValue of one UChooserTable column, the cell value rows appended by add_chooser_row inherit; set it before adding rows. The fields that apply depend on the column type (see the params); others are ignored. A change is one undo step and is compiled and saved, and success is false, with save_error, when the save fails; a value the column already holds changes nothing (already_existed true, saved false).

Returns: { table_path, column_index, column_type, default_value?, asset_path?, comparison?, already_existed, saved, save_error? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoFloatRange column: default upper bound of the row's float range.
minNoFloatRange column: default lower bound of the row's float range.
valueNoEnum and OutputEnum columns: enum ordinal (clamped to 0-255); Name column: the name string to compare; MultiEnum column: the bitmask as an integer.
b_no_maxNoFloatRange column: when true, disables the upper bound (row matches any value >= min).
b_no_minNoFloatRange column: when true, disables the lower bound (row matches any value <= max).
asset_pathNoObject/OutputObject column: long package path of the UObject bound as the default row value.
class_pathNoObjectClass column: path of the UClass to match (e.g. "/Script/Engine.Pawn" or "/Game/BP_Enemy.BP_Enemy_C"), used with comparison (default SubClassOf).
comparisonNoEnum and Name columns: "MatchEqual", "MatchNotEqual", "MatchAny" or "Modulus"; ObjectClass column: "Equal", "NotEqual", "SubClassOf" (default), "NotSubClassOf" or "Any". Case-insensitive.
table_pathYesLong package path of an existing UChooserTable.
column_indexYes0-based column index to update.
default_valueNoBool column: "MatchFalse", "MatchTrue" or "MatchAny"; OutputFloat: a number; OutputBool: a bool; OutputName: a name string; Randomize: a probability weight. Ignored by other column types.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • addedInput schema / properties / class_path / description
      Added value: +"ObjectClass column: path of the UClass to match (e.g. \"/Script/Engine.Pawn\" or \"/Game/BP_Enemy.BP_Enemy_C\"), used with comparison (default SubClassOf)."
    • changedInput schema / properties / comparison / description
      Previous value: -"Enum column: default comparison operator, one of \"MatchEqual\", \"MatchNotEqual\", \"MatchAny\", \"Modulus\"."New value: +"Enum and Name columns: \"MatchEqual\", \"MatchNotEqual\", \"MatchAny\" or \"Modulus\"; ObjectClass column: \"Equal\", \"NotEqual\", \"SubClassOf\" (default), \"NotSubClassOf\" or \"Any\". Case-insensitive."
    • changedInput schema / properties / default_value / description
      Previous value: -"Bool column: default cell match, one of \"MatchFalse\", \"MatchTrue\", \"MatchAny\"."New value: +"Bool column: \"MatchFalse\", \"MatchTrue\" or \"MatchAny\"; OutputFloat: a number; OutputBool: a bool; OutputName: a name string; Randomize: a probability weight. Ignored by other column types."
    • changedInput schema / properties / value / description
      Previous value: -"Enum column: default enum ordinal to compare against (clamped to 0-255)."New value: +"Enum and OutputEnum columns: enum ordinal (clamped to 0-255); Name column: the name string to compare; MultiEnum column: the bitmask as an integer."
    • changedInput schema / required
      Previous value: -[
-  "table_path",
-  "column_index",
-  "default_value"
-]New value: +[
+  "table_path",
+  "column_index"
+]
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Discloses rich behavior beyond the annotations: a change is one undo step, it is compiled and saved, failure yields success=false with save_error, and a redundant value yields already_existed=true/saved=false. This is consistent with (and enriches) the idempotentHint=true and destructiveHint=true annotations rather than contradicting them.

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 the sequencing rule, then packs semantics, save/failure behavior, and the return shape. Dense but essentially every clause carries information; the inline Returns block is long but substitutes for a missing output schema.

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?

For a complex 11-parameter mutation tool with no output schema, the description compensates well by inlining the return shape and error semantics. The dependency on column type is flagged but the mapping lives in the schema, leaving minor room for fuller completion.

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 11 parameters (min/max/b_no_min, value, asset_path, class_path, comparison, default_value). The description only adds the meta-rule that applicable fields depend on column type and others are ignored, which is helpful framing but not new per-parameter meaning.

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?

Specific verb+resource: 'Set the DefaultRowValue of one UChooserTable column', and it clarifies the inheritance semantics (rows appended by add_chooser_row inherit it). An agent can readily distinguish this from sibling tools like set_chooser_row_outcome, add_chooser_row, or add_chooser_column_to_table.

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 a clear ordering rule ('set it before adding rows') and notes that only column-type-matching fields apply. It does not explicitly name an alternative tool or when-not-to-use, so it falls short of the 5-level explicit alternatives guidance, but the context is unambiguous.

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