Skip to main content
Glama

unreal_analyze_asset_dependencies

Analyze asset dependencies in an Unreal Engine 5 project to identify what an asset references and what references it, supporting safe refactoring and cleanup.

Instructions

Analyze asset dependencies.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.9/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. "Analyze" weakly implies a read-only operation, but the description does not state whether it mutates state, how deep or expensive the traversal is, whether results are cached, or what limits apply — all material for a graph-traversal call in an editor.

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?

One short sentence with no wasted words, but the terseness here is under-specification rather than concision. There is no structure to front-load because there is no content beyond the title echoed back.

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-value documentation is not strictly required. However, with a fully opaque parameter and no indication of what the analysis covers or costs, the definition is not complete enough for an agent to invoke it correctly or prefer it over siblings.

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 sole required parameter is an untyped object literally named "params" with 0% schema description coverage, and the description adds no meaning whatsoever. Neither the schema nor the prose tells the agent what to put in it — asset path, package name, GUID, recursion flags — making the tool effectively uncallable from the definition alone.

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 asset dependencies" essentially restates the tool name (unreal_analyze_asset_dependencies) with no added specificity. It never says what the analysis produces — depth, cycle detection, unresolved-reference reporting — nor how it differs from the sibling unreal_get_asset_dependencies, which an agent would plausibly confuse it with.

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 when-to-use guidance and no exclusions or alternatives named. The sibling list contains at least three closely overlapping tools (unreal_get_asset_dependencies, unreal_get_asset_references, unreal_analyze_blueprint_relationships), and the description gives the agent nothing to choose between them.

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