Skip to main content
Glama
Tann2019

Godot Forge

by Tann2019
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Editor & connection

editor

Inspect and control the live Godot workspace: status, logs, undo/redo, notifications, settings, project connections, restarts, and add-on installation.

Instructions

Editor state and connection management: status, logs, undo/redo, notifications to the user, editor settings, and which Godot project/editor this server talks to.

Actions:

  • status: {} edited scene, selection, playing?, connected clients, log counts.

  • logs: {since?, level?: 'error'|'warning', source?: 'editor'|'game', limit?} editor + game output.

  • clear_logs: {} clear the captured log buffer.

  • undo: {steps?=1} undo AI or user edits in the edited scene.

  • redo: {steps?=1}

  • notify: {message} show a toast to the user in the editor.

  • main_screen: {name: '2D'|'3D'|'Script'|'AssetLib'}

  • get_setting: {name} editor setting.

  • set_setting: {name, value}

  • forge_settings: {set?: {autosave?, auto_changeset?, screenshot_max_size?}} Godot Forge behaviour.

  • restart: {save?=true} restart the editor (after enabling plugins, changing rendering method...).

  • connection: {} which project/editor is connected, Godot version, running editors.

  • use_project: {path} switch to another Godot project folder (launches its editor if needed).

  • install_addon: {path?, force?} copy/update the Godot Forge add-on in a project and enable it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSetting or screen name.
pathNoProject folder.
levelNo'error' or 'warning'.
sinceNoLog sequence number to read after (from a previous 'last_seq').
stepsNoHow many steps.
valueNo
actionYesWhat to do. See the tool description for each action's parameters.
sourceNo'editor' or 'game'.
messageNoText to show.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations provide coarse safety hints (readOnlyHint false, destructiveHint false). The description adds per-action behavioral detail beyond annotations: clear_logs empties the buffer, restart defaults save=true, install_addon copies and enables the add-on, and use_project launches an editor if needed. It does not state which actions are read-only versus mutating, but it does not contradict the annotations.

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?

Front-loaded with a one-sentence summary, then a scannable per-action list that packs parameter details without waste. For a 14-action multiplexer, this structure is efficient and every line contributes invocation guidance.

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?

Given the flat schema and absence of an output schema, the description is nearly complete for correct invocation, covering all actions with their parameters and defaults. A minor gap is that it does not indicate which actions return what data or are read-only, but the annotations and schema cover enough for selection.

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

Parameters4/5

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

Schema coverage is 89%, so the schema already documents most parameters. The description still adds meaningful value by mapping parameters to specific actions and supplying defaults (steps=1, save=true) and allowed values (main_screen options, level/source values) that are absent or less specific in the schema. It also documents parameters like limit, force, and nested forge_settings that the schema does not list, compensating for gaps.

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 resource and scope: editor state and connection management, listing domains like status, logs, undo/redo, settings, and project connection. An agent can identify this as the editor-control tool, but the description does not explicitly differentiate it from siblings such as 'project' or 'scene' when their responsibilities overlap.

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 action list implies when each action is appropriate (e.g., 'notify' to show a toast, 'use_project' to switch projects), giving implied usage. However, there is no explicit guidance on when to choose this tool over siblings like 'project' or 'run', and no exclusions or preconditions 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