Loading ToolBench
MCP Server to create and draw .vox models file locally
VoxBuilder has 4 tools with basic schemas and descriptions, but significant gaps prevent production use. All tools have descriptions (10-80 chars, below the 194-char baseline), and input schemas are present with Zod validation. However, descriptions lack actionable context (WHEN to use, prerequisites, state changes). Parameters are minimally described. No output schemas documented. Error handling is absent, tools will crash silently on missing models or invalid paths. The 'setVoxels' tool accepts optional color but doesn't explain that null removes voxels (buried in description). No pagination, no recovery guidance, no per-item error reporting for batch operations.
create a .vox model project
export a .vox model project to a local file path
get voxel blocks from a model project, use this to know what you have done
set voxel blocks to a model project by pos and rgba color
No output schemas documented. LLMs cannot plan downstream operations or extract structured data from responses. getVoxels returns JSON string, not typed object.
No error handling or recovery guidance. Tools will crash if model doesn't exist (models[name] is undefined) or path is invalid. No actionable error messages for LLM.
Descriptions are too short (10-80 chars vs 194-char baseline) and lack context. 'set voxel blocks to a model project by pos and rgba color' doesn't explain when to use it, that null color removes blocks, or what happens on invalid input.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
Parameter descriptions are minimal. 'pos' object lacks explanation of coordinate system, bounds, or integer requirement. 'color' object doesn't document RGBA ranges (0-255? 0-1?) or that null removes the voxel.
No validation of numeric ranges. Coordinates and RGBA values are unconstrained, LLM could pass negative coords, RGBA > 255, or floats where integers required. No min/max constraints in schema.