Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

export_scene_asset

Export selected or full Blender scenes to glTF/GLB, FBX, USD, OBJ, STL, PLY, or ABC with overwrite protection and file verification.

Instructions

Exports scene objects to an industry-standard 3D file format (glTF/GLB, FBX, USD/USDC/USDA, OBJ, STL, PLY, ABC) with overwrite protection and post-export file verification.

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": {
      "filepath": "<filepath>"
    },
    "name": "export_scene_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport format: 'GLTF', 'GLB', 'FBX', 'USD', 'USDC', 'USDA', 'OBJ', 'STL', 'PLY', 'ABC'. Auto-detected from file extension if omitted.
task_idNoOptional task or workflow identifier.
approvedNoDEPRECATED / UNTRUSTED: Client-supplied approval flags in tool arguments are not trusted as proof of human consent.
filepathYesAbsolute output destination filepath on disk.
overwriteNoWhether to allow overwriting an existing destination file. Defaults to False.
selected_onlyNoWhether to export only currently selected objects. Defaults to False (entire scene).
generate_sidecarNoWhether to generate a SHA-256 sidecar file (.sha256). Defaults to True.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose two important behaviors — overwrite protection and post-export file verification — which the agent could not infer from the schema alone. It omits other relevant traits: required filesystem permissions, what happens on a verification failure, whether partial files are left behind, and what the call returns.

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?

It is a single front-loaded sentence with no filler, and the key behaviors are stated up front. The long parenthetical format list is somewhat redundant against the schema enum, which keeps it from being maximally tight.

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

Completeness4/5

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

For a 7-parameter export tool with full schema coverage and no output schema, the description covers the core contract: destination, format, overwrite behavior, and verification. It stops short of explaining the sidecar output, selection-scope effects, or the return value, which leaves a modest gap for an agent that must reason about results.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented, including format auto-detection from the extension and the overwrite/selected_only defaults. The description's format enumeration merely restates the schema enum and adds no semantics beyond it, so baseline 3 applies.

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 opens with a specific verb and resource ('Exports scene objects') and enumerates the supported output formats, so the agent knows exactly what the tool produces. It does not, however, distinguish this tool from the sibling 'export_scene', leaving the agent to guess which exporter is appropriate.

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 exclusions, and no mention of alternatives such as 'export_scene' or 'import_scene_asset'. The only usage signal is implicit in the format list, which the schema already supplies.

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