Skip to main content
Glama

unreal_validate_assets

Validate Unreal Engine 5 assets to detect invalid or broken references before editing, building, or running editor workflows through an AI client.

Instructions

Validate assets.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/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 and delivers none of it: it does not say whether validation mutates anything, whether it is read-only or expensive, whether it requires the editor to be running, or what happens on failure. The two-word description discloses no behavioral traits at all.

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?

Two words and a period — no waste, but the brevity reflects under-specification rather than economy. Nothing is front-loaded because nothing is stated.

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 values need not be explained, but for a validation tool whose input is an opaque "params" object and which has zero annotation coverage, the definition leaves the agent unable to construct a valid call with confidence. This is materially incomplete relative to the tool's role.

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

Parameters1/5

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

The single required parameter is an untyped wrapper object named "params" with 0% schema description coverage, and the description says nothing about what belongs inside it (asset paths, a filter, a validation profile). With the schema entirely silent, the description had to compensate and does not.

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

Purpose2/5

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

"Validate assets" restates the tool name (unreal_validate_assets) with no additional specificity — no indication of what 'validate' checks (references, naming, import settings, dependency integrity) or which asset scope. It also fails to distinguish this tool from siblings such as unreal_validate_blueprints, unreal_validate_project, or unreal_validate_actor_placement.

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 when-to-use guidance, no preconditions, and no pointer to alternatives. An agent cannot tell from the description whether this validates a single asset, a folder, or the whole project, nor why it would choose this over unreal_validate_project.

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