Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

ingest_external_uassets

Destructive

Copy external .uasset/.uexp/.ubulk/.umap files into the project Content, preserve relative paths, register packages, and fix redirectors.

Instructions

Copy .uasset/.uexp/.ubulk/.umap from an EXTERNAL Content tree into THIS project, preserving each file's path relative to its Content root, then register the new packages with IAssetRegistry::ScanPathsSynchronous(bForceRescan) and sweep object redirectors under the destination. Fills the gap that migrate_assets only EXPORTS and import_asset is FBX/PNG-only. HEAVY: touches project Content on disk + mutates the registry -- run with confirmation.

Returns: { source_dir: string, content_root: string, dest_root: string, dest_dir: string, files_copied: int, files_skipped: int, files_failed: int, scanned_paths: [string], redirectors_fixed: int, copied: [{src, dest, package_path}], message: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsNoOptional list of relative sub-paths (relative to the Content root) to restrict the copy to; empty/absent = whole tree.
dest_rootNoDestination content mount path (optional, default '/Game'); e.g. '/Game/MyGame/Imported'.
overwriteNoOptional bool (default false). When false, destination files that already exist are skipped.
source_dirYesExternal source directory (its Content ancestor defines the preserved relative path; if none, source_dir itself is the root).
fixup_redirectorsNoOptional bool (default true). Resolve + leave-fixed object redirectors under dest_root after the copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so safety is partly covered. The description adds real behavioral context beyond that: it touches project Content on disk, mutates the asset registry via ScanPathsSynchronous, and sweeps redirectors, plus a confirmation warning. Skip/overwrite dynamics come from the schema, so this is solid but not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Dense but front-loaded with the core action, then the differentiator, then the warning. The Returns block is long but informative given no output schema. Slightly verbose, yet every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a heavy mutation tool with no output schema, the description supplies an explicit return shape (counts, scanned_paths, redirectors_fixed, copied entries) and covers the registry/redirector side effects. Nothing an agent needs to invoke it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100%, so the schema already documents all five parameters including defaults. The description adds the relative-path preservation rule but little else about parameter semantics. Baseline 3 is appropriate when the schema carries the weight.

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

Purpose5/5

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

States a specific verb+resource (copy .uasset/.uexp/.ubulk/.umap from external Content tree into this project) plus the scope of what it preserves and registers. It also names the siblings it is not (migrate_assets, import_asset) and why it exists, so an agent can distinguish it without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly positions the tool against the alternatives: 'Fills the gap that migrate_assets only EXPORTS and import_asset is FBX/PNG-only.' This tells the agent when this is the right pick. It adds a HEAVY/confirmation warning, though it does not state an explicit when-not-to-use case.

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