Goxel-MCP

Overview Schema Source Related Servers Discussions Admin

Export

goxel_export

Export a voxel scene to gox, vox, OBJ, glTF, PNG, or other formats; the file extension selects the format so models open in Blender or MagicaVoxel.

Instructions

Export the scene. Native formats: gox, vox, obj, txt, png (obj + mtl is the simplest choice for Blender; vox for MagicaVoxel). With Goxel's own exporters (needs the Goxel build with the bridge): gltf, glb, ply, qubicle, kv6, kvx, vxl, povray (gltf / glb also open in Blender). The format is deduced from the file extension when omitted.

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": {
      "path": "<path>"
    },
    "name": "goxel_export"
  }
}

Input Schema

Name	Required	Description
`path`	Yes	Destination file relative to the workspace
`scale`	No	.obj: size of one voxel in output units
`format`	No
`validate`	No
`overwrite`	No
`merge_layers`	No	.vox: merge all layers into one model (default: one model per layer)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 25, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations, so the description carries the full burden. It usefully discloses that the extra exporters require 'the Goxel build with the bridge', which is a genuine environmental prerequisite. It says nothing about overwrite behavior, what 'validate' does, or whether export fails on an existing file.

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?

Front-loads the core action in one short sentence, then groups format information logically by native vs Goxel-bridge exporters. The parenthetical asides carry useful information rather than filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter file-writing tool with no annotations and no output schema, format coverage is strong but two behaviorally significant parameters (validate, overwrite) and the failure/overwrite semantics are not addressed, leaving an agent unable to predict what happens on existing destinations.

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 50%: path, scale, and merge_layers are documented in the schema, and format has none. The description compensates for the format gap by stating the extension is deduced when the format is omitted. The validate and overwrite parameters remain undocumented in both schema and description.

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 ('Export') and resource ('the scene'), then enumerates the concrete output formats. It does not, however, distinguish this from the sibling goxel_save_scene, so an agent must infer the export-vs-save boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real selection guidance among formats: 'obj + mtl is the simplest choice for Blender; vox for MagicaVoxel' and notes gltf/glb also open in Blender. It lacks any guidance on when to prefer this over goxel_save_scene, but format choice is well covered.

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

Deploy Server