Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

execute_game_script

Runs GDScript code inside a live game session to test logic or modify behavior at runtime.

Instructions

Execute arbitrary GDScript code in the running game context.

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

Input Schema

NameRequiredDescriptionDefault
codeYesGDScript code to execute at runtime

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?

With no annotations, the description carries the full disclosure burden, and for an arbitrary-code-execution tool that is a major gap. It never says whether execution is sandboxed, what side effects persist in the running game, whether it can crash or hang the session, what is returned, or how errors surface.

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?

One sentence, front-loaded with verb and resource, no filler or redundant restatement of the parameter. Nothing could be cut without losing content.

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?

For an arbitrary-code-execution tool with no annotations and no output schema, the definition should say what the call returns, how failures are reported, and what safety envelope exists. None of that is present, leaving the agent unable to predict the result of invoking it.

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 coverage is 100% with a single documented 'code' parameter, so the schema already does the heavy lifting; baseline is 3. The description adds only 'at runtime', which is minimal but consistent with the runtime context already stated.

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 states a specific verb (Execute) and resource (arbitrary GDScript code) plus a scope qualifier (in the running game context), which is enough to separate it from editor-side siblings like run_editor_script. It stops short of explicitly naming that sibling, so an agent must infer the contrast.

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 running game context' implicitly signals when this tool applies (live game vs. editor scripting), but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is inferable rather than 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