VoxelForge

Overview Schema Source Related Servers Discussions Admin

voxelforge_export_roblox_merged

Exports merged voxel objects as a single Roblox Part to reduce lag by combining multiple voxels into one model.

Instructions

Export Luau สำหรับ Roblox — รวม voxel เป็น Part ใหญ่ใน Model เดียว (ลดแลag). ใช้ Roblox_Studio MCP execute_luau (Edit mode) รันโค้ดที่ได้

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_roblox_merged"
  }
}

Input Schema

Name	Required	Description	Default
`scene_name`	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

A3.5/5.0

Behavior4/5

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

No annotations provided, but description discloses key behavioral traits: it generates Luau code (not a file), combines voxels into a single Model to reduce lag, and requires running in Roblox Studio. This adds good context beyond the schema.

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?

Description is two concise sentences with no superfluous text. The first sentence front-loads the core function, the second provides a usage hint. Every word earns its place.

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 the complexity (export tool with optional params and an output schema), the description is incomplete: it does not mention that parameters are optional, what happens if omitted, or what the output schema contains. Sibling tools are many but differentiation is minimal.

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

Parameters1/5

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

Schema has 2 parameters with titles but 0% description coverage. The tool description does not explain what scene_name or output_path are for, leaving agents without guidance on their meaning or usage.

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?

Description clearly states it exports Luau for Roblox, merging voxels into one large Part in a single Model to reduce lag. This is a specific verb+resource combination and distinguishes from other export tools like export_obj.

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?

Description provides a direct instruction to use Roblox_Studio MCP execute_luau to run the code, but does not explicitly state when to use this tool versus alternatives or exclude any cases.

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