Skip to main content
Glama

blender_splatting

Import, clean, and optimize 3D Gaussian splats from real-world captures. Prepare splats for VR platforms like Resonite by cropping, generating collision meshes, and adjusting for performance.

Instructions

Advanced Gaussian Splatting (3DGS) management for hybrid environments.

Supports importing real-world captures, cleaning them up, and preparing them for VR platforms like Resonite for immersive experiences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationNoSplatting operation typeimport_gs
file_pathNoPath to .ply or .spz splat file (for import_gs)
target_formatNoExport format ("ply" or "spz")ply
crop_typeNoCrop volume type ("sphere", "box", "cylinder")sphere
radiusNoRadius/size of crop volume
center_pointNoCenter point for cropping
invert_cropNoWhether to invert crop selection
density_thresholdNoMinimum density for collision mesh generation
decimation_ratioNoMesh simplification ratio (0.1 = 10% of faces)
smoothing_iterationsNoLaplacian smoothing passes
sh_degreeNoSpherical harmonics degree (0-3)
setup_proxyNoCreate performance proxy for large splats
include_collisionNoExport collision mesh with splat
optimize_for_mobileNoApply mobile VR optimizations

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It does not mention side effects, permissions, or safety. The term 'Advanced' lacks specifics. Minimal transparency.

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?

Two sentences, front-loaded with key purpose. Could be more concise by removing vague terms like 'hybrid environments', but overall efficient.

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?

With 14 parameters and no output schema shown, the description omits many operations (e.g., create_proxy, optimize_for_vr). It covers only importing, cleaning, and VR prep, leaving the full scope unclear.

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%, so baseline is 3. The description adds no extra meaning beyond the schema; it only provides a high-level overview without explaining parameter relationships or usage.

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 mentions 'Gaussian Splatting management' and lists importing, cleaning, and VR preparation. It distinguishes from general Blender tools but could be more specific about the range of operations (e.g., cropping, collision mesh).

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?

No guidance on when to use this tool vs alternatives like 'agentic_blender_workflow' or 'intelligent_3d_processing'. The description only mentions hybrid environments and VR platforms, but no exclusions or comparisons.

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