Skip to main content
Glama

unreal_find_unused_assets

Identifies unused assets in an Unreal Engine project using a bounded scan, helping you locate candidates for cleanup before deleting or reorganizing content.

Instructions

Find unused assets (bounded scan).

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 disclosure burden and largely drops it. The parenthetical '(bounded scan)' hints that the search is capped but never says what the bound is, how long it runs, whether results are truncated, or whether the operation is read-only.

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?

Brevity here reads as under-specification rather than economy. Two words plus a parenthetical leave the core questions unanswered, so the size is not appropriate to the complexity of the task.

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 explanation is not required. Everything else is missing: no parameter guidance for the single opaque argument, no behavioral disclosure in the absence of annotations, and no routing among the many find_/list_/search_ 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 coverage is 0% and the single parameter is an opaque 'params' object with no properties documented. The description adds nothing about what that object should contain (scope paths, asset classes, scan limits), leaving the caller with no way to construct a valid call.

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 phrase 'Find unused assets' gives a verb and a resource, so the basic intent is legible. But 'unused' is never defined (unused by what reference set?) and the definition makes no attempt to distinguish itself from nearby siblings such as unreal_find_missing_references or unreal_find_duplicate_assets.

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, no exclusions, and no named alternative. An agent looking for asset-hygiene checks has to guess whether this or unreal_find_missing_references / unreal_validate_assets is the right entry point.

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