Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

get_sequence_possessables

Read-onlyIdempotent

List possessable bindings for a Level Sequence by asset name under /Game, returning GUID, name, class, parent GUID, and count.

Instructions

List the possessable bindings of a Level Sequence found by asset name under /Game (first match): GUID, name, possessed class and parent GUID of each, plus possessable_count. Read-only; spawnables are listed by get_sequence_spawnables, and every binding with its tracks by get_sequence_bindings.

Returns: { sequence_name: string, possessables: [{guid, name, class, parent_guid}], possessable_count: int }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequence_nameYesAsset name (not a path) of the Level Sequence, e.g. "LS_Intro"; the first match under /Game is used, ignoring case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / sequence_name / description
      Previous value: -"Name of the level sequence asset."New value: +"Asset name (not a path) of the Level Sequence, e.g. \"LS_Intro\"; the first match under /Game is used, ignoring case."
  2. First observedv1.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the first-match case-insensitive resolution and the exact return shape, though it omits behavior when no asset matches.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the verb and resource in the first sentence, then the routing alternatives, then a compact Returns line. No filler; every sentence carries information.

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 compensates by spelling out the return shape (sequence_name, possessables with guid/name/class/parent_guid, possessable_count). Combined with annotations covering safety, nothing an agent needs to call this 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 single param's syntax is already documented. The description reinforces the resolution rule (asset name under /Game, first match), which adds mild context beyond the schema but not much that isn't already there.

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 and resource (List the possessable bindings of a Level Sequence), names the lookup scope (asset name under /Game, first match), and explicitly distinguishes itself from get_sequence_spawnables and get_sequence_bindings. An agent can differentiate the three sibling tools without inspecting schemas.

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?

Routes the agent with explicit alternatives: spawnables go to get_sequence_spawnables, and every binding with its tracks goes to get_sequence_bindings. This makes the when-to-use decision unambiguous for a family of closely-named sequence tools.

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