VoxelForge

by thanakon228

Overview Schema Source Related Servers Discussions Admin

Python

Local

voxelforge_place_many

Place multiple voxels from a JSON array specifying coordinates and either color hex codes or palette indices.

Instructions

วางหลาย voxel จาก JSON array. รูปแบบ: [[x,y,z,"1"], [1,0,0,"2"], ...] หรือใช้ #RRGGBB เป็นสี

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "blocks_json": "<blocks_json>"
    },
    "name": "voxelforge_place_many"
  }
}

Input Schema

Name	Required	Description	Default
`scene_name`	No
`blocks_json`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 28, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description bears full burden. It only states 'place many voxels' and gives input format, but fails to disclose side effects (e.g., overwriting, layer handling, scene requirement, or confirmation). Minimal behavioral context.

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 lines providing purpose and a concrete example. No unnecessary words, though could benefit from separating parameter explanations.

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?

For a batch operation tool with two parameters and an output schema, the description lacks details on scene_name, output, constraints (e.g., max array size), and error conditions. Major gaps for practical use.

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?

Schema coverage is 0%, so description should compensate. It explains the format for blocks_json with an example but ignores scene_name entirely. Thus, only partial compensation for one parameter.

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 the tool places multiple voxels from a JSON array, contrasting with the sibling tool voxelforge_place_block for single placement. The verb 'วาง' and resource 'หลาย voxel' are specific.

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 explicit guidance on when to use this tool versus alternatives. Only indirect differentiation via the tool name and sibling list. No when-not or prerequisite information.

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