Skip to main content
Glama

unreal_import_blender_fbx

Import Blender-exported FBX files into Unreal Engine with built-in validation to catch format or asset issues before adding them to a project.

Instructions

Import an FBX exported from Blender with validation.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.8/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. It never says what 'validation' checks, what happens when validation fails, whether a partially imported asset is left behind, or what permissions or editor state are needed. For a mutation tool that writes into a project, this is a significant gap.

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?

One short sentence, front-loaded with the verb and resource, and free of filler. The brevity comes at the cost of substance, but nothing in the wording is wasted.

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

Completeness3/5

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

The output schema exists, so return values need not be explained. Still, for an import tool with an entirely undescribed parameter object, the description leaves out too much about inputs and failure behavior.

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 parameter is an opaque 'params' object with 0% schema description coverage, and the description adds no detail about its fields or their formats. The agent gets no hint whether this holds an FBX path, import options, or validation toggles.

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: import an FBX that was exported from Blender, with validation. That is clear enough to distinguish it from generic asset import. However, it never contrasts itself with near siblings such as unreal_reimport_blender_asset or unreal_import_asset.

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?

The phrase 'exported from Blender' implies the source constraint, but the description says nothing about when to use this instead of reimport or plain import. It also gives no prerequisites, no mention of how it relates to unreal_validate_blender_import, and no 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