Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

add_select_node

Creates a Blueprint Select node with the required number of option pins using option_count or an enum, then returns all pin names for wiring.

Instructions

Create a Select node with the RIGHT NUMBER OF OPTION PINS: pass option_count to grow beyond the built-in 2, or an enum in enum_path so one option pin is generated per enum entry and the Index pin becomes that enum. add_graph_node node_type="select" only ever makes the plain 2-option wildcard version. The response names the index pin, the return pin and every option pin, so the branches can be wired without a follow-up read. Its pins stay WILDCARD until something is connected (connect_pins reconstructs the node to re-type them).

Returns: { node_id, pins:[...], blueprint_name, graph_name, index_pin, return_value_pin, option_pins:[string], option_count, index_enum? }

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.
enum_pathNoOptional enum path/name to drive the Index pin (option pins are then auto-generated per enum entry). An engine enum may live in an unexpected module -- ask the enum itself with static_enum().get_path_name() rather than guessing /Script/Engine.
graph_nameNoTarget graph name; defaults to the Blueprint's event graph when omitted.
index_typeNoAlias of enum_path (an enum path/name for the Index pin).
position_xNoNode X position (ignored when node_position is set).
position_yNoNode Y position (ignored when node_position is set).
option_countNoOptional total number of option pins to end up with (default = the node's built-in 2; capped internally at a safe growth loop). Ignored when an enum drives the index.
node_positionNoNode canvas position as [x, y]; takes precedence over position_x/position_y.
blueprint_nameNoBlueprint name or path.
blueprint_pathNoAlias of `blueprint_name` (same value, same meaning). Accepted because sibling tools spell this parameter differently; prefer `blueprint_name`.

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 this is a non-read-only, non-idempotent, non-destructive mutation, so the safety profile is covered. The description adds genuine behavioral context beyond that: pins remain WILDCARD until something is connected, connect_pins reconstructs the node to re-type them, and the response names the index/return/option pins. It does not contradict any annotation.

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?

It is front-loaded with the key instruction (the all-caps emphasis on getting the option-pin count right) and ends with a compact Returns line. The prose is dense but every sentence carries information; the all-caps emphasis is a minor style cost.

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 10-parameter mutation tool with no output schema, the description covers the two pin-generation modes and even enumerates the response fields (node_id, pins, index_pin, return_value_pin, option_pins, etc.). Combined with full schema coverage, an agent has enough to call and consume the tool; only the PIE-refusal behavior lives in the schema rather than the description.

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; the description earns above baseline by adding cross-parameter semantics not in the schema, namely how enum_path overrides option_count and turns the Index pin into an enum, and that enum_path can be discovered via static_enum().get_path_name().

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 opening sentence states a specific verb and resource (Create a Select node) and immediately differentiates from the sibling add_graph_node node_type="select", which it explicitly says only makes the plain 2-option version. An agent can distinguish the two 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?

It gives explicit when-to-use branching: option_count to grow beyond the built-in 2, or enum_path to auto-generate one pin per enum entry and drive the Index pin, plus the condition (option_count ignored when an enum drives the index). It also names the alternative (add_graph_node) and the case it does not cover.

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