Skip to main content
Glama

unreal_get_actor_relationships

Inspect actor relationships in Unreal Engine 5 projects to identify attachments, ownership, and dependencies for debugging and level design.

Instructions

Inspect actor relationships.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden, yet it only implies a read-like operation through the word "inspect." It does not state that the call is read-only, whether it requires specific editor state or permissions, or whether it has side effects.

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

Conciseness3/5

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

The description is a single front-loaded sentence with no wasted wording, which is structurally clean. However, its brevity reflects under-specification rather than disciplined conciseness, since almost nothing useful is conveyed.

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 the tool still has an entirely undocumented parameter object and no annotations. For an inspection tool surrounded by many similar sibling tools, the description is too thin to support correct selection and invocation.

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 no defined properties. The description adds no meaning about what belongs in that object, such as an actor identifier or relationship-type filter.

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?

"Inspect actor relationships" restates the tool name with a vague verb and an undefined resource; it never specifies what kind of relationships (attachment, ownership, references, hierarchy) are returned. It also fails to distinguish the tool from close siblings such as unreal_get_actor_components, unreal_get_actor_details, or unreal_analyze_blueprint_relationships.

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?

The description offers no when-to-use guidance, no exclusions, and no named alternative. An agent cannot tell from this text whether to call it instead of unreal_get_actor_components or unreal_get_actor_details.

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