VoxelForge

by thanakon228

Overview Schema Source Related Servers Discussions Admin

Python

Local

voxelforge_export_obj

Export 3D voxel models as Wavefront .obj files. Merge adjacent voxels into single boxes for optimized output.

Instructions

Export เป็น Wavefront .obj — merge_boxes=true รวม voxel ติดกัน (แนะนำ).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "voxelforge_export_obj"
  }
}

Input Schema

Name	Required	Description	Default
`scene_name`	No
`merge_boxes`	No
`output_path`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

There are no annotations, so the description must fully disclose behavior. It only explains the merge_boxes option but does not mention performance, side effects, or whether the operation is destructive.

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?

The description is very short and to the point, consisting of one sentence. It is concise but could be structured better (e.g., bullet points) for clarity.

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?

Given no annotations and three parameters, the description is incomplete. It only covers one parameter partially and does not mention the output format or return value, despite an output schema existing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning for merge_boxes only. The other two parameters (scene_name, output_path) are not explained. Schema coverage is 0%, so the description could have compensated but failed to do so.

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 this tool exports to Wavefront .obj format and explains the merge_boxes parameter. It is distinct from sibling tools like export_vox and export_obj_legacy.

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 mentions that merge_boxes=true is recommended, implying a usage hint. However, it does not explicitly state when to use this tool over siblings or when not to use it.

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