Skip to main content
Glama
Sign In
Godot MCP - Full Control

Godot MCP - Full Control

by cxb2523
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_script

Generates a GDScript file in a Godot project from a template, letting you set base class, class name, and method stubs or provide full source code.

Instructions

Create a GDScript file from a template

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": {
      "projectPath": "<projectPath>",
      "scriptPath": "<scriptPath>"
    },
    "name": "create_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoFull source code (overrides template)
extendsNoBase class to extend. Default: Node
methodsNoMethod stubs to include
classNameNoOptional class_name
scriptPathYesScript file path (relative to project)
projectPathYesGodot project path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/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 behavioral burden. It does not disclose whether an existing script at scriptPath is overwritten or rejected, whether the target directory is created automatically, or what the tool returns on success. The only behavioral hint is template-based generation, which the 'source' parameter already suggests at the schema level.

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?

A single front-loaded sentence with no filler. It is efficient, but the brevity reflects under-specification rather than disciplined economy given the tool's mutation semantics.

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 file-mutating tool with six parameters, no annotations, and no output schema. The one-line description does not cover overwrite behavior, failure modes, or the result of the call, which an agent needs before invoking it against an existing project.

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%, so all six parameters including source, extends, methods, and className are already documented in the schema. The description adds only the template framing, which ties loosely to the 'overrides template' note on source; it contributes no further parameter meaning.

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 and resource ('Create a GDScript file') and adds that it is template-based, which distinguishes it from a generic file write. It does not, however, differentiate from close siblings such as create_csharp_script, attach_script, or write_file, leaving the agent to infer which creation path to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus create_csharp_script (other language), attach_script (attach to an existing node), or write_file (raw file creation). Usage is only implied by the tool name and the word 'template'.

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