Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

execute_editor_script

Execute GDScript within the Godot editor to automate workflows, manipulate scenes, and control project operations programmatically.

Instructions

Execute GDScript in editor context. (Compatibility tool)

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

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 full disclosure burden. It fails to mention that additionalProperties allows passing arbitrary script arguments, does not clarify if the script execution can modify editor state destructively, and omits what the timeoutMs/autoConnect parameters control.

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 extremely concise with only two sentences. While efficient, the '(Compatibility tool)' parenthetical is under-explained given the complexity of script execution, making the description feel incomplete rather than appropriately brief.

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?

Given the tool accepts arbitrary additional properties (likely script arguments) and lacks annotations or output schema, the description is inadequate. It fails to explain the parameter passing mechanism, return behavior, or safety implications of running arbitrary GDScript in the editor.

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

Parameters1/5

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

With 0% schema description coverage, the description must compensate by explaining the timeoutMs and autoConnect parameters and the critical additionalProperties behavior. It mentions none of these, leaving users unaware that arbitrary script arguments can be passed.

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 clearly states the core action (Execute GDScript) and the specific context (editor context), which distinguishes it from the sibling 'execute_game_script'. The '(Compatibility tool)' qualifier provides additional classification, though its specific meaning is opaque.

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 'editor context' phrase implies usage for editor automation vs runtime, but there is no explicit guidance on when to choose this over 'execute_game_script' or what 'Compatibility tool' signifies in terms of deprecation or specific use cases.

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