Skip to main content
Glama

unreal_get_actor_details

Retrieve detailed information about a specific actor in an Unreal Engine 5 project, including its properties and state, to inspect or debug scene contents.

Instructions

Get detailed actor information.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and adds almost nothing: it does not state that the operation is a safe read, what categories of data are returned, or whether the actor must exist / be in the current world. The only behavioral signal is the verb "Get", which is already in the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The sentence is short and front-loaded, but its brevity reflects under-specification rather than efficiency. There is no wasted wording, yet the single sentence communicates no more than the tool name already does.

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 in prose, which relieves some burden. However, the input schema is a single undescribed object and there are no annotations, so the definition leaves the agent unable to determine how to address an actor or what class of data it will receive.

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

Parameters1/5

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

The single required parameter is an opaque "params" object with 0% schema description coverage, and the description says nothing about what it must contain (actor reference? name? path? handle?). This is the worst case for parameter semantics: an undocumented wrapper the agent cannot construct with confidence.

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

Purpose2/5

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

"Get detailed actor information" essentially restates the tool name unreal_get_actor_details without defining what "detailed" covers. It does not distinguish the tool from close siblings such as unreal_get_actor_components, unreal_get_actor_transform, or unreal_get_actor_relationships, so an agent cannot tell which one returns which slice of actor data.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of any alternative tool. The agent is left to guess whether this is the general actor-inspection entry point or overlaps with the transform/component/relationship getters.

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