Skip to main content
Glama
aadeshrao123

Unreal-MCP

by aadeshrao123

set_data_asset_property

Set a single property on a data asset, supporting all types including primitives, structs, arrays, and object references. Includes special handling for MassEntity trait configurations.

Instructions

Set a single property on a data asset.

Supports all types: primitives, enums, FName, FText, structs ({"tagName": "..."}), arrays, object refs ("/Game/..."), soft refs, and None (clears reference).

property_name is case-sensitive (exact FProperty name).

Mass Entity Config — Editing Trait Properties: To edit trait properties on a MassEntityConfigAsset (e.g., BeltSpeed, SlotCount), set property_name="Config" with a JSON value containing the Traits array. Each trait needs a "_ClassName" with FULL path "/Script/Module.ClassName".

Example — set BeltSpeed on a conveyor config: set_data_asset_property( asset_path="/Game/.../DA_ConveyorMassConfig_Mk2", property_name="Config", property_value={ "Traits": [{"_ClassName": "/Script/Jiggify.MassConveyorBeltTrait", "BeltSpeed": 200}] } )

IMPORTANT: _ClassName MUST be full path ("/Script/Jiggify.MassConveyorBeltTrait"), NOT short name ("MassConveyorBeltTrait"). Short names create wrong base class. For configs with multiple traits, include ALL traits in the array (entire array is replaced). Only set the properties you want to change — others use C++ defaults.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asset_pathYes
property_nameYes
property_valueYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Given no annotations, the description covers supported types, clears reference with None, and warns about full path requirements and array replacement. It does not disclose undoability or save behavior but is generally transparent.

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?

The description is well-structured with sections and examples, front-loading the main purpose. The MassEntityConfig section is detailed but justified given complexity; minor verbosity prevents a perfect score.

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

Completeness4/5

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

The description covers core functionality, parameter details, and special cases. It assumes asset existence and lacks mention of side effects or requirements, but the presence of an output schema reduces the need to explain return values.

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

Parameters5/5

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

With 0% schema coverage, the description adds essential meaning to all three parameters: asset_path (implied), property_name (case-sensitive), and property_value (types, examples, JSON structure for MassEntityConfig).

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 clearly states the tool sets a single property on a data asset, distinguishing it from sibling tools like set_data_asset_properties that set multiple properties. Examples and special cases reinforce the purpose.

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?

The description provides explicit usage context, including case-sensitivity, supported types, and detailed instructions for MassEntityConfig assets. It lacks explicit comparison with similar tools like set_asset_property but implicitly differentiates from set_data_asset_properties.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadeshrao123/Unreal-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server