Skip to main content
Glama

blender_splatting

Import real-world captures, clean, crop, generate collision meshes, and export Gaussian splats for VR platforms like Resonite.

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 are provided, and the description does not disclose behavioral traits such as side effects, required permissions, or whether operations are destructive. The high-level description lacks detail on how the tool behaves during execution.

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 two sentences, front-loading the core purpose without extraneous information. It is appropriately sized for the tool's complexity.

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?

With 14 parameters and no annotations, the description is relatively sparse. It covers the overall workflow but does not provide context about parameter interactions or output expectations. An output schema exists but is not referenced.

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 the input schema already documents all 14 parameters. The description adds no additional parameter meaning beyond summarizing the operations as import, cleanup, and VR preparation.

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 that the tool manages Gaussian Splatting for hybrid environments, covering import, cleanup, and VR preparation. It distinguishes itself from sibling tools like blender_import or blender_mesh by specifying a niche workflow for 3DGS.

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 Gaussian Splatting tasks but does not explicitly contrast with alternatives like blender_import or blender_render. No direct when-to-use or when-not-to-use guidance is provided.

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