Skip to main content
Glama

blender_export_presets

Export and validate 3D avatars with platform-specific presets for VRChat, Resonite, and Unity. Adjusts scale, format, and bone limits automatically for correct VR deployment.

Instructions

Platform-specific export presets for VR avatar deployment.

Handles the critical differences between VR platforms (scale, format, bone limits) ensuring your avatars work correctly in VRChat, Resonite, and Unity environments.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoExport preset operation typeexport_with_preset
target_objectsNoList of object names to export/validate
platformNoTarget VR platform ("VRCHAT", "RESONITE", "UNITY", etc.)VRCHAT
output_pathNoExport output path (without extension)//export
include_materialsNoInclude materials in export
include_texturesNoInclude textures in export
apply_modifiersNoApply modifiers before export
check_bonesNoValidate bone count and naming in validation
check_materialsNoValidate material compatibility in validation
check_scaleNoValidate scale settings in validation
preset_nameNoName for custom preset creation
base_platformNoPlatform to base custom preset onVRCHAT
custom_settingsNoCustom settings for preset creation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the transparency burden. It mentions handling scale, format, and bone limits, but does not disclose whether the tool modifies the scene, requires permissions, or has side effects. Adequate but incomplete.

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?

Two sentences, highly concise, front-loaded with the main purpose. Every sentence adds value without redundancy.

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 description is too high-level for a tool with 13 parameters and multiple operations (export, validate, get presets, create custom). It does not mention the different operation types or provide enough context for the agent to understand the full scope.

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 coverage is 100% with parameter descriptions. The description does not add additional meaning beyond the schema for individual parameters, so baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool provides platform-specific export presets for VR avatar deployment, explicitly naming VRChat, Resonite, and Unity. It distinguishes from the sibling 'blender_export' by focusing on platform-specific presets rather than general export.

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?

The description implies usage for VR avatar deployment with platform-specific adjustments, but it does not explicitly state when to use this vs alternatives like 'blender_export'. No when-not-to or exclusion criteria are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sandraschi/blender-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server