Skip to main content
Glama

unreal_search_assets

Search Unreal Engine assets by name or class to find project resources for inspection, editing, and Blueprint or level workflows.

Instructions

Search assets by name/class.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the whole burden of behavioral disclosure. It does not state that the operation is read-only, whether results are paged or capped, what happens with an empty or unmatched query, or what kind of asset records come back.

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

Conciseness3/5

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

The definition is a single front-loaded sentence with no filler, so nothing needs to be cut. The problem is under-specification rather than verbosity; a tool with an opaque parameter object warrants at least one more sentence on how to query.

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?

Given an undisclosed parameter object, no annotations, and the presence of a diverse sibling set, the definition is too thin for reliable invocation. The output schema does relieve it of explaining return values, but query construction and result scope remain unexplained.

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 opaque 'params' object with no documented properties. The phrase 'by name/class' hints that name and class are the filter keys, but it gives no syntax, wildcard behavior, or mapping of those keys to the schema, so it only partially compensates for the coverage gap.

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

Purpose4/5

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

The description names a specific verb (search) and resource (assets) plus the searchable facets (name/class), which is clearer than a bare restatement of the tool name. It does not, however, distinguish this tool from siblings such as unreal_list_assets, unreal_get_skeleton_assets, or the unreal_find_* family, leaving overlap in purpose ambiguous.

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 search instead of unreal_list_assets or the find_* tools, and no statement of prerequisites or exclusions. The agent must infer selection criteria purely from names.

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