Skip to main content
Glama

unreal_import_asset

Imports an external asset file into an Unreal Engine 5 project, letting AI clients add textures, meshes, and other resources to the editor's content browser.

Instructions

Import an external asset file.

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_import_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 disclosure burden and adds almost nothing: it does not state whether an import overwrites existing assets, where files must live, which formats are accepted, or what happens on name collision. An output schema exists, so return values needn't be explained, but the write-side behavior of a mutation tool is essentially undisclosed.

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?

The sentence is syntactically short but not concise in the useful sense: it is under-specified rather than economical. A single vague line with no front-loaded constraints provides no structure an agent can act on.

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?

For a mutation tool taking an undocumented free-form parameter, the definition omits nearly everything needed: accepted file types, source paths, destination asset paths, and overwrite semantics. Only the existence of an output schema relieves it of explaining results.

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 single required parameter is an opaque wrapper named "params" with 0% schema description coverage and no nested structure defined, and the description offers no field names or format hints. An agent has no information at all about what to place inside this object to perform an import.

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 specific verb and resource ("Import" + "asset file"), so the general action is identifiable. However, "external asset" is left undefined and nothing distinguishes this from siblings like unreal_import_blender_fbx or unreal_reimport_asset, leaving ambiguity about which import path applies.

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 prerequisites, and no indication of when another sibling (e.g., unreal_reimport_asset for existing assets, unreal_import_blender_fbx for FBX pipelines) should be preferred. The agent must guess based on the name 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