Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

set_state_type

DestructiveIdempotent

Change a StateTree state's type (State, Group, Linked, LinkedAsset, Subtree) and save the asset without recompiling, so you can adjust its role in the tree.

Instructions

Set the type of a StateTree state (EStateTreeStateType: State, Group, Linked, LinkedAsset or Subtree) and save the asset without recompiling it. An unknown name is an error. To point a state at another tree prefer set_state_linked_asset, which also sets the linked asset.

Returns: { tree_path, state_name, state_type, set, saved }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tree_pathYesAsset path of the StateTree, e.g. "/Game/AI/ST_Guard".
state_nameYesName of the state to change; the command fails without it.
state_typeYesEnum value name: State, Group, Linked, LinkedAsset or Subtree (an EStateTreeStateType:: prefix is accepted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.2.0
    • changedInput schema / properties / state_name / description
      Previous value: -"Name of the state to modify"New value: +"Name of the state to change; the command fails without it."
    • changedInput schema / properties / state_type / description
      Previous value: -"One of State | Group | Linked | LinkedAsset | Subtree"New value: +"Enum value name: State, Group, Linked, LinkedAsset or Subtree (an EStateTreeStateType:: prefix is accepted)."
    • changedInput schema / properties / tree_path / description
      Previous value: -"Asset path to the UStateTree"New value: +"Asset path of the StateTree, e.g. \"/Game/AI/ST_Guard\"."
    • changedInput schema / required
      Previous value: -[
-  "tree_path",
-  "state_type"
-]New value: +[
+  "tree_path",
+  "state_name",
+  "state_type"
+]
  2. First observedv1.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (destructive=true, idempotent=true, readOnly=false). The description adds real value beyond them: it discloses that the asset is saved without recompiling, that an unknown name is an error, and the shape of the returned fields. It does not cover permissions or rollback behavior, keeping it short of a 5.

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 main action is front-loaded in the first sentence, followed by the error condition, then the sibling routing, then a compact Returns line. Every sentence earns its place, though the Returns line is arguably redundant given the 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 destructive mutation tool with annotations present and no output schema, the description is complete enough: it explains the mutation, the save-without-recompile side effect, error handling, and the return shape. Only permissions/reversibility context is absent.

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 three parameters (path format, state name, enum values with prefix note). The description's enumeration of enum values and the failure-without-name note largely duplicate the schema. Baseline 3 is appropriate.

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 ('Set') plus the exact resource ('the type of a StateTree state'), enumerates the valid enum values, and distinguishes itself from the sibling set_state_linked_asset. An agent can identify the operation and its scope 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to an alternative: 'To point a state at another tree prefer set_state_linked_asset, which also sets the linked asset.' This names both the when-to-use-this and the when-to-use-sibling condition, leaving nothing to inference.

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