Skip to main content
Glama
Sign In
Goxel-MCP

Goxel-MCP

by yberudev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

New scene

goxel_new_scene

Create a new empty voxel scene; unsaved changes are autosaved to backups first.

Instructions

Create an empty voxel scene. If the current scene has unsaved changes, an autosave is written to .goxel-mcp/backups/ first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "goxel_new_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
layer_nameNoName of the first layer (default: 'Layer 1')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does address the central risk: unsaved changes trigger an autosave to .goxel-mcp/backups/ before the new scene is created. It still leaves open whether the prior scene is discarded irreversibly and whether the operation is undoable.

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?

Two sentences, front-loaded with the action and followed by the one caveat that matters. Nothing is wasted.

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

Completeness4/5

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

For a one-parameter creation tool with no output schema and no annotations, this covers purpose and the main data-safety behavior. A note on whether the old scene is closed or return values would make it complete.

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 description coverage is 100%, and the single optional layer_name parameter is fully documented in the schema. The description adds no meaning beyond that, so baseline 3 applies.

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: 'Create an empty voxel scene.' The word 'empty' implicitly distinguishes it from goxel_open_scene, though no sibling is named explicitly.

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?

Usage is implied by the name and the 'empty' qualifier, but the description never states when to use this versus goxel_open_scene or goxel_save_scene, nor any prerequisites.

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