Skip to main content
Glama

unreal_validate_blender_import

Validates Blender export conventions for Unreal imports, helping catch naming and setup issues before assets are imported.

Instructions

Validate Blender export conventions for Unreal.

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

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/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 of disclosure. 'Validate' hints at a read-only check, but the description does not state whether the tool mutates anything, what rules or conventions it checks, whether it blocks an import, or what happens on failure. The output schema covers the shape of the result, but the runtime and safety behavior is still undocumented.

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?

It is a single tight sentence with no filler, which is structurally clean. However, this brevity comes at the cost of under-specification rather than economy: there is no front-loaded detail to orient the agent beyond the tool name restated in sentence form.

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?

For a validation tool with an opaque single params object, no annotations, and no sibling differentiation, the description is too thin to be complete. The output schema saves it from being entirely opaque on results, but the input contract and usage trigger remain unexplained.

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?

There is one required parameter named generically 'params' with 0% schema description coverage and no nested object details. The description gives no hint about what belongs in that object (a file path, an options dict, an asset reference), so the caller has essentially nothing to work with beyond the schema, which is itself empty.

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 has a specific verb (Validate) and a specific resource (Blender export conventions for Unreal), so the agent knows the general category of operation. It does not distinguish this from the other validators it sits beside (unreal_validate_assets, unreal_validate_blueprints, unreal_validate_project), which leaves the exact scope of the validation 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 tool instead of the import tools (unreal_import_blender_fbx, unreal_reimport_blender_asset) or the other validators. Should it run before an import, after an export, or as a standalone audit? The description does not say.

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