Skip to main content
Glama

unreal_get_asset_references

Retrieves all assets that reference a given asset, helping you identify dependencies and safely manage changes before deleting or modifying it.

Instructions

Get asset referencers.

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

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, yet it only weakly implies a read-only retrieval via the verb 'Get'. It says nothing about scope (whole project vs. loaded assets), whether it is an expensive deep scan, or whether it searches derived/redirected references.

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 short, but short by under-specification rather than by efficiency — a four-word sentence that conveys no information beyond the tool name.

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 explained, but with no annotations and a completely undocumented parameter, the definition leaves the agent without enough to call this tool correctly or to choose it over its reference-related 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?

Schema description coverage is 0% and the single required parameter is an opaque untyped 'params' object. The description adds no meaning about what to put in it (asset path, package name, filter flags), so an agent cannot construct a valid call from description plus schema.

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?

The description 'Get asset referencers' restates the tool name rather than explaining it. It never distinguishes 'referencers' (assets that point at this asset) from the sibling unreal_get_asset_dependencies (assets this asset points at), which is the key distinction an agent must make.

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 named alternative, even though unreal_get_asset_dependencies and unreal_find_missing_references sit right next to it. The agent must infer the difference from tool names alone.

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