Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_consideration_property

Read-onlyIdempotent

Read a single property from a StateTree consideration node by reflection without editing the asset; returns its JSON value, C++ type, and has_value. Use list_considerations first to get the index.

Instructions

Read one property of a consideration node on a StateTree state by reflection, without changing the asset. Returns the value as JSON with its C++ type and has_value; only node struct properties are reachable, not instance data. Find the index with list_considerations.

Returns: { tree_path, state_name, consideration_index, property, type, value, has_value }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
propertyYesName of a property on the consideration node struct; case-insensitive.
tree_pathYesAsset path of the StateTree, e.g. "/Game/AI/ST_Guard".
state_nameYesName of the state that owns the consideration; the command fails without it.
consideration_indexYes0-based index into the state Considerations, as listed by list_considerations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.2.0
    • changedInput schema / properties / consideration_index / description
      Previous value: -"0-based index."New value: +"0-based index into the state Considerations, as listed by list_considerations."
    • changedInput schema / properties / property / description
      Previous value: -"FProperty name."New value: +"Name of a property on the consideration node struct; case-insensitive."
    • changedInput schema / properties / state_name / description
      Previous value: -"Name of the state."New value: +"Name of the state that owns the consideration; the command fails without it."
    • 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",
-  "consideration_index",
-  "property"
-]New value: +[
+  "tree_path",
+  "state_name",
+  "consideration_index",
+  "property"
+]
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the reflection mechanism, the limitation that only node struct properties are reachable (not instance data), and the returned type/has_value pair.

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 scope in the first sentence, then appends the limitation and discovery hint. The trailing 'Returns:' line largely restates what the body already implies, but overall it is tight and earns most of its length.

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?

With no output schema, the description carries the return-shape burden and does so by enumerating the returned fields and noting the reachability limitation. Combined with annotations that cover the safety profile, an agent has enough to invoke it correctly.

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 all four parameters are already documented in the schema, establishing the baseline of 3. The description adds only the pointer to list_considerations for sourcing the index; it contributes no syntax or format detail beyond the schema.

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 (read), resource (one property of a consideration node on a StateTree state), and mechanism (by reflection, without changing the asset). The 'one property' scope cleanly distinguishes it from the sibling get_consideration_info, which reports on the consideration as a whole.

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?

Provides clear operational context by naming the discovery prerequisite ('Find the index with list_considerations'), which is essential for supplying the required consideration_index. It stops short of an explicit when-to-use-vs get_consideration_info / set_consideration_property contrast, so it lands at clear-context without exclusions.

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