Skip to main content
Glama

scene_find_actor

Read-only

Searches actors in a saved .scene or .prefab file by partial name or full type name, ignoring case; use it to inspect on-disk files without opening the editor.

Instructions

Searches the actors of a saved .scene or .prefab file on disk. Name matches a part of the actor name, TypeName matches the full type name, and both ignore case. The tool does not need the editor and does not see unsaved changes. It returns the first 100 matches. For the scenes in the running editor, use editor_find_actors.

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": {
      "path": "<path>"
    },
    "name": "scene_find_actor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
pathYes
typeNameNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses important behavioral traits: the tool does not need the editor, it cannot see unsaved changes, and it returns only the first 100 matches. It does not cover error behavior for missing paths, but the read-only annotation and result cap provide substantial transparency.

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?

The description is short, front-loaded with the main action, and each sentence adds useful information: scope, matching rules, editor-independence, unsaved-change limitation, result cap, and sibling alternative.

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?

For a read-only search tool with an output schema available, the description covers the essential context: on-disk vs editor state, matching semantics, result limit, and the relevant alternative tool. Nothing critical for correct invocation 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?

With 0% schema description coverage, the description carries the burden and explains that name does case-insensitive partial matching while typeName requires the full type name and is also case-insensitive. The required path parameter is implied by 'saved .scene or .prefab file on disk' but is not further specified, leaving a minor gap.

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?

The description states a specific verb and resource: it searches actors within a saved .scene or .prefab file on disk. It also explicitly distinguishes this from editor_find_actors, which handles scenes in the running editor, so an agent can identify the correct tool without opening 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?

It clearly states when to use this tool versus the main alternative: saved on-disk scenes/prefabs use scene_find_actor, while running-editor scenes use editor_find_actors. It also warns that unsaved editor changes are invisible, which is a key usage constraint.

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