Skip to main content
Glama
TechBot_Blender_MCP

TechBot_Blender_MCP

by bharatnextai

export_scene

Export scene objects to glTF, GLB, FBX, USD, OBJ, STL, PLY, or ABC with overwrite protection and post-export file verification to confirm output integrity.

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

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.3/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 behavioral burden. It usefully discloses overwrite protection and post-export file verification, but it does not explain what verification entails, whether permissions are required, what side effects occur on overwrite, or what the return behavior is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that names the action, resource, supported formats, and two key safeguards. Every phrase contributes useful information with no filler.

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?

For a seven-parameter export tool with no annotations and no output schema, the description covers the core purpose and some behavioral safeguards. However, it omits return-value expectations, details of the verification step, and guidance on selection versus full-scene export beyond what the schema already states.

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 all seven parameters are already documented in the schema. The description reinforces the format list and overwrite protection, but adds no syntax, constraints, or meaning beyond what the schema provides.

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 states a specific verb ('Exports') and resource ('scene objects') and enumerates the supported 3D file formats. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling export_scene_asset, leaving the agent to infer the scope difference.

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 explicit guidance on when to use this tool versus alternatives such as export_scene_asset or import_scene. The purpose implies an export operation, but no conditions, exclusions, or prerequisites are stated.

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