Godot MCP Assistant

create_gdscript

Create GDScript files in a Godot project, optionally generating starter scripts or movement examples for CharacterBody2D and CharacterBody3D nodes.

Instructions

Create a GDScript file inside a Godot project. If content is omitted, generate a starter script; CharacterBody2D and CharacterBody3D get working movement examples.

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_gdscript"
  }
}

Input Schema

Name	Required	Description	Default
`content`	No	Optional complete GDScript source. An extends declaration is added when missing and must match baseClass when present.
`baseClass`	No	Godot base class, for example Node, CharacterBody2D, Area2D, or CharacterBody3D.	Node
`overwrite`	No	Replace an existing file. Defaults to false.
`scriptPath`	Yes	Path to the new .gd file relative to projectPath.
`projectPath`	Yes	Absolute path to a directory containing project.godot.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Oct 20, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries full disclosure burden. It usefully reveals that omitting content yields a starter script and that CharacterBody2D/3D get working movement examples, which is real behavioral value. However, it never states what happens when the target file already exists and overwrite is false (error? silent no-op?), nor any permission/path requirements, leaving notable gaps for a mutating tool.

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?

Two tight sentences, front-loaded with the core action before the conditional behavior. Every clause carries information; nothing is restated from the title or schema.

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?

There is no output schema, so return values need not be explained, and the generation behavior is covered. But with no annotations on a file-writing tool, the description should address the pre-existing-file case and error/failure behavior; those omissions leave an agent guessing at a critical edge case.

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?

Schema coverage is 100%, so baseline is 3, and the description earns a bump by tying the 'content' parameter to concrete fallback semantics ('if content is omitted, generate a starter script' with movement templates for physics bodies) that the schema does not spell out. It still says nothing about overwrite or baseClass interaction beyond what the schema documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a GDScript file inside a Godot project') and the .gd resource is plainly distinct from siblings like generate_tscn_scene or inject_script_autoload. The second sentence further characterizes the tool by describing its default-generation behavior, so an agent can identify it without opening the schema.

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: an agent infers this is the tool for producing a .gd source file. There is no explicit when-to-use/when-not framing, no mention of how it relates to inject_script_autoload (which also targets .gd files), and no stated prerequisites. The conditional 'if content is omitted' clause is behavior, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server