Skip to main content
Glama

unreal_reimport_blender_asset

Reimport a previously imported Blender asset into Unreal Engine to update the existing project asset after making changes in Blender.

Instructions

Reimport a previously imported Blender asset.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and discloses almost nothing. It does not say whether reimport overwrites the existing asset, preserves overrides, requires source-file access or a running Blender instance, or can fail and how. Only the bare fact of the operation is conveyed.

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?

A single short sentence with no filler, and the key qualifiers are front-loaded. It is efficient, though so terse that it reads closer to under-specification than to deliberate brevity.

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?

The output schema covers return values, so that need not be explained. However, with an opaque single parameter, no annotations, and no discussion of overwrite behavior or source-file requirements, the definition leaves too much unknown for a reimport tool that mutates existing assets.

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?

The single required parameter is an untyped "params" object with 0% schema description coverage and no listed properties. The description only hints that the parameter identifies a previously imported Blender asset, giving the agent no usable detail about what to put inside it.

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?

States a specific verb and resource (reimport a Blender asset) plus a precondition ("previously imported") that implies an existing import record. The Blender qualifier implicitly distinguishes it from the generic unreal_reimport_asset, but the description never names that sibling or states the distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied through the phrase "previously imported," which tells the agent an existing import must exist first. There is no explicit guidance on when to choose this over unreal_reimport_asset or unreal_import_blender_fbx, and no stated prerequisites or exclusions.

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