VoxelForge

by thanakon228

Overview Schema Source Related Servers Discussions Admin

Python

Local

voxelforge_place_block

Place a single voxel at specified 3D coordinates with optional color in a voxel model scene.

Instructions

วาง voxel 1 ลูกที่พิกัด (x,y,z).

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "voxelforge_place_block"
  }
}

Input Schema

Name	Required	Default
`x`	Yes
`y`	Yes
`z`	Yes
`color`	No	1
`scene_name`	No

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 carries full burden. It only states basic action without disclosing side effects (e.g., overwriting existing voxels), coordinate bounds, or permission requirements. Minimal behavior revealed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence is concise and front-loaded, but it lacks necessary structure and detail. It achieves conciseness at the expense of completeness, potentially confusing agents needing more context.

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?

With 5 parameters (3 required) and no output schema descriptions, the description does not cover return values, error conditions, or optional parameter usage. It is inadequate for an agent to confidently invoke this tool.

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 description coverage is 0%, yet the description adds no information about color or scene_name parameters. Coordinates are mentioned but not elaborated (units, bounds). The description fails to compensate for missing schema descriptions.

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 one voxel at given coordinates (x,y,z). It uses specific verb 'place' and resource 'voxel', distinguishing it from sibling tools like voxelforge_place_many which places multiple.

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 guidance on when to use this tool vs alternatives (e.g., place_many for bulk, fill_box for area). No mention of prerequisites or context, leaving the agent with no usage direction.

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