VoxelForge

by thanakon228

Overview Schema Source Related Servers Discussions Admin

Python

Local

voxelforge_set_active_layer

Set the active layer by index (starting from 0) to target editing operations on that layer in a 3D voxel model scene.

Instructions

ตั้ง layer ที่ใช้งาน (index เริ่ม 0).

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": {
      "index": "<index>"
    },
    "name": "voxelforge_set_active_layer"
  }
}

Input Schema

Name	Required	Description	Default
`index`	Yes
`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 are provided, so the description must disclose behavioral traits. It only states the basic action but does not explain behavior on invalid index, side effects (e.g., subsequent operations affect the active layer), return value, or error handling.

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?

Extremely concise (one sentence). However, the brevity sacrifices clarity on parameters and behavior. Still, it is front-loaded and to the point.

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 tool modifies state and has an output schema, the description lacks context on what happens after execution (e.g., success indication, effect on other operations). It does not address potential errors or preconditions.

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%, so description should clarify parameters. It explains 'index' but does not mention the optional 'scene_name' parameter or its role. The description adds minimal value beyond the schema.

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's action ('set active layer') and specifies that index starts at 0. This distinguishes it from sibling tools like add_layer (adds a new layer) or clear (clears all layers).

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 or when not to. No mention of prerequisites (e.g., scene must exist) or alternatives among siblings.

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