Skip to main content
Glama

unreal_delete_asset

Deletes an Unreal Engine asset to remove unwanted or unused content from the project.

Instructions

Delete an asset.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.1/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 discloses nothing about whether the deletion is permanent, undoable, prompted for confirmation, or cascading to dependent assets. The single word "delete" at least signals a destructive mutation, but an agent gets no operational safety context at all.

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 sentence is front-loaded and contains zero filler, so there is nothing to trim. The problem is under-specification rather than verbosity, which is penalized in the other dimensions rather than here.

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?

For a destructive mutation with one required but completely undocumented parameter object and no annotations, the definition leaves the agent unable to determine correct invocation. The presence of an output schema removes the need to describe return values, but everything else an agent needs is missing.

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 untyped nested "params" object with no properties defined. The description offers no indication of how the target asset is identified (path, name, GUID), so the meaning of the lone parameter is documented nowhere.

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?

"Delete an asset" states a verb and a resource, so the basic action is unambiguous. However, it adds essentially nothing beyond the tool name, and it never clarifies whether an actor, blueprint, or material expression counts as an "asset" here, which matters given siblings like unreal_delete_actor and unreal_delete_blueprint that operate on asset-like objects.

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 prerequisite (e.g., check references first via unreal_get_asset_references), and no warning about irreversibility. The agent must infer entirely on its own when this is the right deletion tool versus unreal_delete_actor or unreal_delete_blueprint.

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