Skip to main content
Glama
Sign In
Goxel-MCP

Goxel-MCP

by yberudev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open in Goxel

goxel_open_in_app

Open a .gox or .vox scene in the Goxel editor. Set live=true to enable live editing through the bridge, or live=false to open the file in the official app without control.

Instructions

Open the scene in the Goxel editor. live=true (the default when the Goxel build with the bridge is available) starts Goxel with the bridge and switches to live editing: the following tool calls modify the scene open in the editor. live=false tries to open the file in the official Goxel app (no control; that app may need File > Open).

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_open_in_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNo
pathNo.gox / .vox file to open (default: the current file of the scene)
timeout_sNo

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 provided, the description carries the burden and discloses important behavior: live=true starts Goxel with the bridge and enables live editing, while live=false opens the official app without control and may require manual File > Open. It does not cover timeout behavior, return values, or what happens if the bridge is unavailable.

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?

The description is front-loaded around the core action and then explains the live-mode tradeoff. It is appropriately sized, though the live explanation is dense and could be easier to scan.

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 tool with no annotations, no output schema, and only partial parameter documentation, the description covers the key live-editing behavior but omits timeout semantics and error/return behavior. It is adequate but has clear gaps.

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 low at 33%; path is documented in the schema, and the description adds substantial meaning for live. However, timeout_s is left unexplained in both the schema and the description, so parameter semantics are only partially covered.

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?

The description states a clear verb and resource: "Open the scene in the Goxel editor." It also distinguishes live editing from opening in the official Goxel app, though it does not explicitly contrast this tool with sibling tools such as goxel_open_scene.

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?

It gives clear conditions for choosing live=true versus live=false, including the consequence that subsequent tool calls modify the open scene. It lacks explicit guidance on when to use this instead of sibling tools like goxel_open_scene or goxel_live.

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