Skip to main content
Glama

unreal_get_all_actors

Lists every actor in the current Unreal Engine world so you can inspect and identify scene objects.

Instructions

List actors in the current world.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "params": "<params>"
    },
    "name": "unreal_get_all_actors"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden and says nothing about behavioral traits: whether the listing is potentially huge in populated levels, whether results are paginated or truncated, whether it requires an editor/PIE session, or whether it is a cheap read. Only the implicit read-only nature of "List" is conveyed.

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?

A single short sentence with the resource and scope front-loaded and no filler. It is efficient, though the brevity is partly a symptom of missing content rather than disciplined editing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, but for a one-required-param tool with zero annotation coverage the description leaves the agent without enough to call it correctly: the params payload is opaque and the listing's cost/scope implications are unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter named "params" with 0% schema description coverage, so its shape and meaning are documented nowhere. The description does not compensate in the slightest, not explaining what the params object should contain or whether it is optional-in-practice filtering.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List actors in the current world" gives a specific verb (List), resource (actors), and scope (current world). It does not, however, distinguish itself from near-identical siblings such as unreal_get_selected_actors or unreal_list_level_actors, leaving the agent to infer the difference from names alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to prefer this tool over unreal_get_selected_actors or unreal_list_level_actors, and no note about when an unfiltered full-world listing is inappropriate. Usage context is only implied by the word "current world".

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