Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_pose_search_runtime_state

Read-onlyIdempotent

Diagnose null motion-matching chooser results by reading live PIE/Game actor AnimInstance, trajectory samples, pose history node, and optional database schema.

Instructions

Read-only report of the live motion-matching state on a PIE/Game actor (why a chooser returns null): its AnimInstance, its MotionTrajectory samples, whether a PoseSearchHistoryCollector node named pose_history_name exists, and (optionally) the target database's schema/channels.

Returns: { world_mode, actor_name, actor_resolved, actor_resolved_by, skeletal_mesh_component, anim_instance_class, pose_history_name, pose_history_found, trajectory:{found,component,property,sample_count,is_trajectory_empty,samples[]}, is_trajectory_empty, database?:{database_path,schema_path,schema_cardinality,channel_count,channels[],animation_asset_count}, note, world_name, world_package, world_type, net_mode, pie_instance }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
worldNoWhich world to resolve: absent (default) = prefer the live PIE/Game world, else the editor world | 'server' (the PIE world with authority -- what a server-driven character lives in) | 'client' | 'pie:N' | 'pie'/'game' force the live session (errors if none running) | 'editor' forces the editor world.
actor_nameNoActor name or label to inspect. Omitted = the first player controller's pawn (the locally-controlled character).
database_pathNoOptional UPoseSearchDatabase asset path; when given, its schema_path/schema_cardinality/channels/animation_asset_count are included.
pose_history_nameNoTag of the PoseSearchHistoryCollector anim-graph node to look up on the AnimInstance (default 'PoseHistory'). A missing node is the usual reason a query builds an empty pose portion.
max_trajectory_samplesNoCap on emitted trajectory samples (<=0 = all; default 0).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds value by clarifying this is a live-state read tied to PIE/Game and by explaining the diagnostic intent (empty pose portion / null chooser), going beyond what the annotations state. It does not mention the world-resolution fallback behavior in the top-level text, but the schema covers that.

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 purpose is front-loaded in one sentence, followed by a structured Returns block. Given there is no output schema, enumerating returned fields is justified rather than wasteful. The Returns block is long but every field earns its place as the only output documentation.

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?

With no output schema, the description supplies the full return shape; all five parameters are documented at 100% schema coverage; annotations cover the safety profile; and the diagnostic use case is stated. An agent has everything needed to select and call 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%, and the schema itself gives rich per-parameter semantics (world modes, actor default, pose_history_name default, sample cap). The description only cross-references pose_history_name and the optional database_path effect, adding little syntax or meaning beyond 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 (report/read) and resource (live motion-matching state on a PIE/Game actor) and immediately frames the purpose with '(why a chooser returns null)'. It enumerates exactly what gets inspected — AnimInstance, MotionTrajectory samples, PoseSearchHistoryCollector node presence, optional database schema/channels — which cleanly distinguishes it from siblings like inspect_pose_search_database or evaluate_pose_search_query that operate on assets rather than live runtime state.

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 a clear diagnostic context (why a chooser returns null) that tells the agent when this tool is the right one. However, it names no alternatives explicitly and offers no when-not guidance, so it sits at clear-context-without-exclusions rather than 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