Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_editor_state

Retrieves the current Godot editor state, including open scene, selected node, and play status, so AI commands can target the correct context.

Instructions

Get the current state of the Godot editor (open scene, selected node, play state, etc.).

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": "get_editor_state"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the content of the snapshot (open scene, selected node, play state), which signals a non-destructive read, but it says nothing about whether the editor must be running, whether the call blocks, or what happens when no scene is open.

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?

One front-loaded sentence with the resource named first and the useful detail in a parenthetical. The trailing 'etc.' slightly undercuts precision by leaving the returned field set open-ended.

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?

With no annotations and no output schema, the description is the only source of information about the response, and its 'etc.' leaves the exact shape undefined. It is adequate for a zero-parameter snapshot getter but not complete enough to tell the agent precisely what it will receive.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify. The parenthetical enumeration of returned state adds a little orientation but no parameter meaning is needed.

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 ('Get the current state of the Godot editor') and enumerates the returned facets (open scene, selected node, play state). It is clear what the tool does, though it never distinguishes itself from close siblings such as get_current_scene or get_editor_screenshot.

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 only implied by the word 'current' — the agent can infer it is a read of live editor state rather than game runtime state, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many get_* siblings.

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