Skip to main content
Glama

unreal_analyze_blueprint_relationships

Analyze Blueprint dependencies and references to map how assets, nodes, or classes connect, helping identify relationship impacts in Unreal Engine projects.

Instructions

Analyze Blueprint 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_analyze_blueprint_relationships"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the operation is read-only, what constitutes a relationship, how deep the traversal goes, whether it can be slow on large Blueprints, or what permissions are needed. 'Analyze' hints at a non-mutating operation but that is inference, not disclosure.

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?

It is certainly short, but brevity here is under-specification rather than economy; there is no front-loaded scope statement, no structural separation, and nothing for the agent to anchor on beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/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 explained, but the description says nothing about which Blueprint is targeted, what analysis is performed, or what the opaque `params` object requires. For a tool whose only input is an undocumented wrapper object, this is inadequate.

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 a bare `params` object with 0% schema description coverage and no nested property documentation, and the description adds no information about what belongs in it. This is the worst case for a tool with a parameter: neither the schema nor the description tells the agent how to construct the call.

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?

"Analyze Blueprint relationships" restates the tool name almost verbatim, giving a verb and resource but no scope, no output meaning, and no distinction from the sibling unreal_get_actor_relationships or unreal_analyze_asset_dependencies. An agent cannot tell what a 'relationship' is here (inheritance? references? dependencies?) or how this differs from the other analyze/get-relationship tools.

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 prerequisites, no exclusions, and no named alternative despite several closely related siblings (unreal_get_actor_relationships, unreal_analyze_asset_dependencies, unreal_get_blueprint). The agent must guess entirely from the name.

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