Skip to main content
Glama

unreal_get_asset_info

Retrieve Unreal Engine asset metadata to inspect properties and details before editing, managing, or validating project assets.

Instructions

Get asset metadata.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.3/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 beyond the bare action: no indication of read-only safety, permission requirements, cost, or whether it works on unloaded assets. An output schema exists, which reduces the need to describe return values, but the description still leaves the operational profile opaque.

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?

At three words it is certainly concise and front-loaded with the verb, but this is under-specification rather than tight writing. There is no wasted text, but there is also almost no information, so the brevity costs more than it saves.

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?

An output schema exists, so return structure need not be spelled out, but for a tool in a large family of near-identically named getters the definition does not supply enough to identify the asset target format or the tool's scope. Relative to the ambiguity created by its siblings, the definition is substantially incomplete.

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

Parameters2/5

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

Schema coverage is 0% and the single parameter is an untyped generic "params" object, so the schema explains nothing. The description does not compensate in any way — it never mentions what the params should contain (asset path, GUID, metadata filter, etc.), which is exactly the gap the description needed to fill.

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 names a specific verb (Get) and resource (asset metadata), so the basic action is clear. However, "metadata" is undefined, and it does not distinguish this from the many sibling getters that also return asset-derived information (unreal_get_mesh_info, unreal_get_asset_dependencies, unreal_get_asset_thumbnail, etc.), leaving the agent to guess what class of metadata this returns.

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 guidance on when to use this tool versus the specialized siblings such as unreal_get_asset_dependencies or unreal_get_mesh_info, and no stated prerequisites (e.g., whether an asset path must be loaded first). The agent gets no selection criteria at all.

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