Skip to main content
Glama

create_script

Creates a GDScript file in a Godot project. Generates a template script with a specified base class and empty _ready(), or writes your full source when provided.

Instructions

Create a GDScript file. Without content, writes a template with the given extends type and an empty _ready().

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

Input Schema

NameRequiredDescriptionDefault
contentNoFull script source; overrides the template
extendsNoBase class, default "Node"
projectYesProject folder name under the projects directory
script_pathYesScript path relative to the project, e.g. "scripts/player.gd"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: omitting content yields a template with the given extends type and an empty _ready(). However, it never states what happens if script_path already exists (overwrite vs error) or whether the project must exist first — critical for a file-writing 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 short sentences, zero filler, with the core action front-loaded and the conditional template behavior immediately after. Nothing in it is redundant or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter creation tool with fully described schema and no output schema, the description covers the main behavioral branch (template vs. full content). The remaining gap is lifecycle behavior on existing files, which matters but is a narrow omission.

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%, so all four parameters are already documented, including the fact that content overrides the template. The description restates that relationship and the extends default without adding format or resolution details, so baseline 3 applies.

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"), which clearly separates it from siblings like create_project, create_scene, and add_node by the artifact produced. It does not explicitly name or contrast a sibling, but the resource noun is unambiguous enough for selection.

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: the second sentence tells the agent what happens when content is omitted, which hints at the two calling modes. There is no explicit when-to-use, when-not, or routing to alternatives such as create_scene for non-script artifacts, so the agent must infer context.

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