Skip to main content
Glama

unreal_get_asset_dependencies

Lists all assets that a specified Unreal Engine asset depends on, helping you trace references and avoid broken links before editing or packaging.

Instructions

Get 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_get_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

C2.4/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 adds nothing beyond the name. It does not confirm read-only behavior, whether results are recursive or depth-limited, or whether unresolved references are reported. Only the generic implication of 'get' suggests a safe read.

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 single short sentence is front-loaded and free of waste, but its brevity is the result of under-specification rather than tight writing. There is no structure to guide the agent beyond the bare action.

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 required, but for a one-parameter tool with a fully untyped schema and no annotations the description is far too thin. An agent cannot tell what to pass in or how this differs from the analyze/references siblings.

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

Parameters2/5

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

Schema description coverage is 0% and the single 'params' object is completely untyped, so the schema supplies no meaning. The description only weakly implies the parameter identifies an asset; it never states the expected identifier form (path, package name, or object reference) or any option like recursion depth.

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

Purpose3/5

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

The description gives a verb and resource (get asset dependencies), so the basic action is identifiable. But it is indistinguishable from the sibling unreal_analyze_asset_dependencies and says nothing about what 'dependencies' means (hard vs soft references, direct vs transitive) or how it differs from unreal_get_asset_references.

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 at all, no exclusions, and no mention of the sibling unreal_analyze_asset_dependencies, which an agent would have to disambiguate from this tool on its own. Usage is only implied by the verb 'get'.

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