Skip to main content
Glama
CarlxsMG

UEAgent

by CarlxsMG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

generate_asset_report

Generate a detailed property report for an Unreal Engine asset, saving it as JSON or TXT. Lists all properties with types and values, counts editable and Blueprint-visible ones, and reports file size without modifying the asset.

Instructions

Load an asset and write a property report to a new file Saved/Reports/Assets/Report<YYYYMMDD_HHMMSS>.json or .txt in the project: every reflected property of its class (editable or not) with its type and value text, counts of editable and Blueprint-visible properties, and the package file size. Those statistics go only into the file; the reply carries its path, size and status. The asset is not modified. A missing asset is an error; an unsupported format writes nothing (report_success=false). export_asset_data writes only editable or Blueprint-visible properties; export_asset_as_text returns a canonical dump inline.

Returns: { asset_path: string, report_format: string, report_success: bool, report_message: string, report_file_path: string, report_file_name: string, report_file_size_bytes: int, report_file_size_mb: number, asset_class: string, package_name: string, report_timestamp: string, report_status: string, report_type: string, report_directory: string }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_pathYesFull path to the asset to analyze (e.g., '/Game/MyAsset').
report_formatYesReport format: 'json' or 'txt'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.4/5.0
Behavior5/5

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

With no output schema, the description carries the behavioral load and does so well: the asset is not modified, missing assets error, unsupported formats silently write nothing with report_success=false, and the timestamped filename implies no overwrite. It also discloses the Return object shape inline. This is consistent with readOnlyHint=false/destructiveHint=false.

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?

Purpose and destination are front-loaded in the first sentence, followed by useful constraints and the Returns block. The paragraph is dense but every clause adds a distinct behavioral fact, so it is appropriately sized for a tool with no output schema.

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?

Given no output schema, the description supplies the full return field list, the write destination, error semantics, and the non-modification guarantee. An agent has everything needed to call it and interpret the result.

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 description coverage is 100%, so both parameters are already documented, and the description adds little beyond restating json/txt and giving the path example. Baseline 3 applies when the schema does the heavy lifting.

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?

The description states a specific verb (load + write) and resource (property report file), with the exact output location and naming convention. It explicitly distinguishes itself from export_asset_data and export_asset_as_text, so an agent can route correctly without opening any schema.

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?

It contrasts the two sibling exporters ('export_asset_data writes only editable or Blueprint-visible properties; export_asset_as_text returns a canonical dump inline'), which tells the agent when to pick this file-writing tool instead. It stops short of an explicit 'use this when' rule, leaving selection partly inferred.

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