Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_editor_sessionsA

List MCP-enabled local Wulfram Forge editors. Select an explicit session ID for subsequent tools.

get_editor_stateB

get_editor_state: read the selected live editor. Inspect returns entity IDs and world-unit coordinates.

inspect_mapA

inspect_map: read the selected live editor. Inspect returns entity IDs and world-unit coordinates.

validate_mapC

validate_map: read the selected live editor. Inspect returns entity IDs and world-unit coordinates.

edit_entitiesA

Atomically add, move or remove ground structures. Coordinates are absolute world units; yaw is radians. mirror:true resolves the unique rotational opponent and applies the opposite transform. New validation errors reject the whole batch. One undo step.

edit_terrainA

Apply one circular terrain brush, optionally rotationally mirrored. Radius/coordinates/heights use world units. Raise/lower value is a nonnegative amount; flatten value is target elevation. Resnaps ground structures and rejects new validation errors. One undo step.

undoA

Undo the selected editor’s last change, including manual changes. Inspect state first; requires current revision.

capture_viewA

Capture the actual current editor viewport and interface as PNG. Does not move the camera.

save_copyA

Save a JSON copy of the exact live revision to a NEW file under outputs/mcp-exports. Does not overwrite files or mark the editor saved.

export_mapC

Export a map ZIP of the exact live revision to a NEW file under outputs/mcp-exports. Does not overwrite files or mark the editor saved.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 10 tools

Disambiguation1/5

get_editor_state, inspect_map, and validate_map all have essentially identical descriptions claiming to read the selected live editor and return entity IDs and world-unit coordinates. An agent cannot reliably distinguish these tools, creating severe selection ambiguity.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern such as capture_view, export_map, edit_entities, and list_editor_sessions. The bare verb 'undo' is a minor deviation but does not create real confusion.

Tool Count4/5

Ten tools is within a reasonable range for an editor-focused MCP server and the overall scope feels manageable. However, the three near-duplicate read tools add unnecessary bulk, making the set slightly less curated than it could be.

Completeness4/5

The server covers session discovery, reading map state, editing entities and terrain, validation, undo, capture, and export/save workflows. It lacks deeper revision history or finer-grained query operations, but the core editing loop is functionally complete.

Maintenance

ActivityMaintained
ResponsivenessNo issues