Skip to main content
Glama

unreal_find_actor

Find actors in an Unreal Engine 5 project by name, label, or class to identify scene objects for inspection and editing.

Instructions

Find actors by name/label/class.

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_find_actor"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about match semantics (exact vs substring, case sensitivity), whether multiple criteria are ANDed, pagination, or behavior when no actor matches. Only the read-only nature of "find" is faintly implied. This is a significant gap for a search tool with zero annotation coverage.

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 no waste, appropriately front-loaded. Its brevity is the only issue only insofar as it reflects under-specification, not padding, but the structure itself is clean.

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?

Complexity is low but the input schema is an opaque untyped 'params' object and there are no annotations, so the description is the only source of contract detail and it supplies none beyond the field hints. The existing output schema removes the need to explain return values, but the calling contract remains underspecified.

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

Parameters5/5

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

Placeholder text for an unassigned witness, ignored.

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?

"Find actors by name/label/class" states a specific verb (find) and resource (actors) plus the lookup keys, so the agent knows it is a search operation. It does not distinguish itself from sibling read tools such as unreal_get_actor_details or unreal_get_actor_components, which also retrieve actor information, so sibling differentiation is absent.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The word "find" only weakly implies lookup rather than retrieval-by-id, leaving the agent to infer that this is the entry point for resolving actors by string criteria.

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