Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

create_script

Create a new GDScript file at a res:// path, optionally add initial code, and attach it to a node. Use it to add scripted behavior during Godot AI-driven development.

Instructions

Create a new GDScript file, optionally with initial content and optionally attach it to a node.

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

Input Schema

NameRequiredDescriptionDefault
pathYesres:// path for the new script
contentNoInitial source code content
attach_toNoNode path to attach the script to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it says nothing about what happens if the res:// path already exists (overwrite vs. error), whether the file is created on disk immediately or saved later, or what is returned. For a filesystem-mutating tool this is a significant gap.

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 compact sentence with no wasted clauses, and the required action is front-loaded. The doubled 'optionally ... and optionally' phrasing is slightly clumsy but not harmful.

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?

For a three-parameter creation tool with no annotations and no output schema, the definition covers the happy path but omits failure modes (existing file, invalid node path) and the return value, which an agent would need to chain a follow-up call.

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 the schema already documents path, content, and attach_to. The description only restates that content and attachment are optional, adding no format details such as whether attach_to requires an existing node or a NodePath syntax.

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 gives a specific verb and resource ('Create a new GDScript file') and notes the two optional behaviors, so an agent knows exactly what artifact is produced. It does not explicitly distinguish itself from near-siblings like create_resource or create_shader, but 'GDScript file' is specific enough to avoid ambiguity.

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 when-to-use or when-not guidance, and no mention of when to use this versus attach_script or edit_script. The phrase 'optionally attach it to a node' hints that attachment is a side effect of creation, but the agent must infer that a separate attach_script call is the alternative.

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