Skip to main content
Glama

editor_find_actors

Read-only

Find actors in the running editor's open scenes, including unsaved changes, by filtering optional name, actor type, and script type; returns IDs, names, types, paths, and script types.

Instructions

Finds actors in the scenes that are open in the running editor (the play-time scene during play), with the unsaved changes. The filters are name, actor type and script type. All are optional, and they combine. Types match by full or short name. Returns id, name, type, path from the scene and the types of the scripts. Truncated is true when more than the limit matched. For a saved .scene or .prefab file without the editor, use scene_find_actor. For the full tree, use editor_scene_graph.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoAt most this many, 1 to 500.
actorTypeNoThe actor's type, e.g. StaticModel or FlaxEngine.Camera.
scriptTypeNoA script type the actor has, e.g. PlayerController.
nameContainsNoPart of the actor's name, case-insensitive.

Output Schema

NameRequiredDescriptionDefault
actorsYes
truncatedYes
mainThreadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.6/5.0
Behavior4/5

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

readOnlyHint is already declared, but the description adds real context beyond it: results reflect unsaved editor state, the play-time scene during play, and a Truncated flag when matches exceed the limit. It also names the returned fields, which goes past what the annotations provide.

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 behavior, then filters, then returns, then alternatives — a logical order with no filler. It is dense with several clauses per sentence, but every sentence carries information an agent needs.

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?

Covers scope, filter combination rules, type-matching behavior, the truncation edge case, and the return fields, and it names the sibling tools for adjacent cases. With an output schema present, the description is complete enough to call the tool correctly in one shot.

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 baseline would be 3, but the description adds non-obvious semantics: all filters are optional and combine, and types match by full or short name. That is meaning the schema does not convey.

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 with scope qualifiers: finds actors in scenes open in the running editor, including play-time scene and unsaved changes. This cleanly separates it from scene_find_actor (saved files) and editor_scene_graph (full tree), both of which are named.

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?

Explicitly routes the agent: use scene_find_actor for a saved .scene/.prefab without the editor, and editor_scene_graph when the full tree is needed. The conditions that select this tool versus the alternatives are stated outright.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.