Skip to main content
Glama
Sign In
Goxel-MCP

Goxel-MCP

by yberudev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move voxels

goxel_transform

Translate voxels in a layer or defined region by an integer offset to reposition model elements precisely.

Instructions

Translate the voxels of a layer (or of a region of it) by an integer offset.

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": {
      "offset": "<offset>"
    },
    "name": "goxel_transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoLayer name or id (default: the active layer)
offsetYes
regionNoRegion: a min/max box and/or a shape

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Translate' implies mutation, but the description does not disclose reversibility, undo behavior, clipping or edge behavior, permissions, or what happens to voxels outside the region.

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?

The description is a single front-loaded sentence with no filler. Every phrase contributes to specifying the operation and its optional scope.

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?

The tool has a nested region schema and no annotations or output schema, yet the description is only one sentence. It omits important behavioral context such as region/offset interaction, mutation effects, and default layer behavior beyond what the schema already states.

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

Parameters3/5

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

Schema coverage is moderate at 67%, and the description adds some meaning by calling the offset an integer translation and clarifying layer/region scope. However, it does not explain the offset array order or units, and the region behavior is left mostly to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: translating voxels of a layer or region by an integer offset. It is clear what the tool does, but it does not explicitly distinguish this move operation from sibling tools such as add, draw, or erase.

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 parenthetical '(or of a region of it)' implies usage for moving existing voxels rather than creating or erasing them, but there is no explicit when-to-use guidance versus alternatives. No prerequisites or exclusions are stated.

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

Deploy Server

Other Tools