Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

run_editor_script

Executes arbitrary GDScript code within the Godot editor context to automate editor tasks and run EditorScript logic.

Instructions

Execute arbitrary GDScript code in the editor context (EditorScript).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "code": "<code>"
    },
    "name": "run_editor_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesGDScript code to execute

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the entire behavioral burden, and it does not disclose what happens on script errors, whether execution is synchronous, whether the script can mutate editor/project state, or whether any result is returned. The word 'arbitrary' hints at broad capability but never spells out the risk profile of running unrestricted code. For an arbitrary-code-execution tool with zero annotation coverage this is a substantial gap.

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?

A single short sentence with zero filler, and the context qualifier is placed where it matters most. Nothing is padded or restated redundantly.

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

Completeness2/5

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

This is a high-risk, unbounded-capability tool with no annotations and no output schema, so the description should explain error behavior, side effects, and what (if anything) comes back. None of that is present, leaving the agent with only the verb and the execution context.

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% for the single 'code' parameter, so the schema already conveys the expected input. The description adds only the framing that the code is GDScript executed as an EditorScript, which is marginal value; the baseline of 3 applies when the schema does the heavy lifting.

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 ('Execute') and resource ('arbitrary GDScript code') and pins the execution context as the editor via '(EditorScript)', which implicitly separates it from the runtime-oriented execute_game_script sibling. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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 phrase 'in the editor context' implies when this is appropriate versus a game/runtime script tool, but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance. An agent must infer the routing decision from the parenthetical alone.

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