Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_input_action_flags

DestructiveIdempotent

Set an InputAction's behavior flags to control how it consumes input, triggers when paused, and interacts with other mappings. Use consume_input carefully to avoid swallowing other actions.

Instructions

Set an InputAction's behaviour flags: consume_input, trigger_when_paused, consumes_action_and_axis_mappings, reserve_all_mappings, the legacy-key consume bitmask, accumulation behaviour and the editor description. Handle consume_input with care -- it is the flag that decides whether OTHER actions on the same key still fire, and turning it on can swallow the game's interaction key entirely, a failure that shows up in an unrelated system days later. Only the fields you pass change, and a call that passes none is an error; the action is saved, and the call succeeds only when it reaches disk. Verify with get_input_action.

Returns: { action_name, action_path, b_consume_input, b_trigger_when_paused, b_consumes_action_and_axis_mappings, b_reserve_all_mappings, trigger_events_that_consume_legacy_keys, accumulation_behavior, action_description, flags_set, saved, save_error? }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
action_nameNoInput action name
action_pathNoAsset path of the Input Action
consume_inputNoWhen set, updates the action's bConsumeInput flag.
action_descriptionNoWhen set, updates the action's ActionDescription (FText) shown in the editor.
trigger_when_pausedNoWhen set, updates the action's bTriggerWhenPaused flag.
reserve_all_mappingsNoWhen set, updates bReserveAllMappings.
accumulation_behaviorNoWhen set, one of "TakeHighestAbsoluteValue" or "Cumulative".
consumes_action_and_axis_mappingsNoWhen set, updates bConsumesActionAndAxisMappings.
trigger_events_that_consume_legacy_keysNoWhen set (int32 ETriggerEvent bitmask), updates TriggerEventsThatConsumeLegacyKeys.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • removedInput schema / required
      Removed value: -[
-  "action_name"
-]
  2. First observedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare the mutation/destructive/idempotent profile, yet the description adds substantial context beyond them: partial-update semantics, the error on empty calls, atomic save-to-disk success condition, and the specific downstream failure mode of consume_input swallowing other actions on the same key. This is exactly the kind of consequence-level disclosure that annotations cannot express.

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 resource and flag list, then the consume_input warning, then the update/save semantics, then the return shape. The opening flag enumeration is a dense comma list and the Returns block is lengthy, but with no output schema that block earns its place and no sentence is filler.

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-parameter mutation tool with no output schema, the description covers the mutation semantics, the error condition, the save behavior, and the return fields. Nothing an agent needs to invoke it correctly is missing.

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 real meaning beyond the schema: it explains what consume_input actually does to other actions, clarifies the legacy-key bitmask role, and names the accumulation behavior values. It doesn't add format/syntax detail for the action_path parameter, so it is slightly above baseline rather than exhaustive.

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 opens with a specific verb+resource ('Set an InputAction's behaviour flags') and then enumerates the exact flags, making it unmistakable which sibling it is versus set_input_action_value_type or set_input_action_trigger_behavior. An agent can identify the tool without opening the schema.

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?

It gives clear operating context (only passed fields change, an empty call is an error) and an explicit verification step with get_input_action, plus a strong caution around consume_input. It does not, however, name the sibling flag-setting tools as alternatives or state when-not to use this one, so it stops short of full routing guidance.

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