Skip to main content
Glama

list_world_partition_actors

Read-onlyIdempotent

Lists all World Partition actors in the editor world by reading descriptors, including spatially unloaded or streamed-out actors, without loading actor packages.

Instructions

Lists the editor world's World Partition actors by walking their DESCRIPTORS without loading any actor package. Unlike get_actors_by_class (which only sees LOADED AActors via TActorIterator), this reads FWorldPartitionActorDescInstance for every actor known to World Partition, INCLUDING spatially-unloaded / streamed-out ones (solving "get_actors_by_class only sees loaded actors"). Editor-world read only (WP actor descriptors are editor-only data); honest empty list on a non-WP (default) map.

Returns: { world: string, is_world_partition: bool, is_initialized: bool, count: int, total_matched: int, truncated: bool, actors: [{ path: string, name: string, label: string, native_class: string, base_class: string, display_class: string, is_spatially_loaded: bool, is_loaded: bool, editor_only: bool, folder: string, runtime_grid: string, editor_bounds: {valid,origin,extent}, runtime_bounds: {valid,origin,extent}, data_layers: [string] }], note: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional int cap on the number of actors returned (default 2000); total_matched reports the full match count regardless of the cap.
folderNoOptional. Case-insensitive substring matched against the actor's editor folder path.
filter_classNoOptional. Class filter: resolved to a UClass (full path, /Script name, Blueprint asset path, or bare A/U name) and matched against each descriptor's native class via IsChildOf; ALSO matched as a case-insensitive substring against the descriptor's native and base class paths (so Blueprint class names like 'BP_Foo_C' or partial names work).
name_containsNoOptional. Case-insensitive substring matched against the actor's label, object name, and soft path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare the safe read profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: it avoids loading actor packages, covers unloaded/streamed-out actors, is editor-only data, and returns an honest empty list on non-WP maps. This is exactly the kind of trade-off and side-effect disclosure annotations cannot carry.

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 core distinction before the mechanical detail, and the Returns block is structured rather than prose. It is dense and long, but with no output schema in play the return enumeration earns its space; only minor tightening is possible.

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?

There is no output schema, so the description supplies the full return shape (world, is_world_partition, count, total_matched, truncated, per-actor fields, note) plus the truncation-vs-total_matched semantics. 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.

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 fully documents limit, folder, filter_class, and name_contains (including the IsChildOf and substring resolution rules). The description adds nothing about parameter meaning beyond what the schema states, so the baseline 3 for high coverage applies.

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 ('Lists the editor world's World Partition actors') and immediately names the mechanism (walking DESCRIPTORS without loading packages). It explicitly contrasts with the sibling get_actors_by_class, so an agent can distinguish the two without opening either 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?

Names the alternative (get_actors_by_class) and the exact condition that selects this tool: the sibling only sees loaded AActors while this tool also returns spatially-unloaded/streamed-out ones. It also scopes usage to editor-world reads and notes the non-WP empty-list behavior. No explicit 'when-not-to-use' beyond the editor-only constraint, so it falls just short of a 5.

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