Skip to main content
Glama

script-create

Creates new GDScript files with optional templates for singleton, state machine, component, or resource patterns to generate game logic scripts.

Instructions

[compact alias of create_script] Creates a new GDScript (.gd) file with optional templates. Use to generate scripts for game logic. Templates: "singleton" (autoload), "state_machine" (FSM), "component" (modular), "resource" (custom Resource).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesAbsolute path to project directory containing project.godot. Use the same path across all tool calls in a workflow.
scriptPathYesPath for new script relative to project (e.g., "scripts/player.gd", "autoload/game_manager.gd")
classNameNoOptional: class_name for global access (e.g., "Player", "GameManager")
extendsNoBase class to extend (e.g., "Node", "CharacterBody2D", "Resource"). Default: "Node"
contentNoOptional: initial script content to add after class declaration
templateNoOptional: template name - "singleton", "state_machine", "component", "resource"
reasonNoOptional reason/context for this change. Displayed in visualizer audit timeline.
Behavior3/5

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

With no annotations provided, the description carries full burden. It mentions optional templates but does not disclose behavior like overwriting existing files, error conditions, or required permissions. The creation action is inherently non-destructive, but missing details limit transparency.

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?

The description is efficient: three sentences cover the purpose, usage, and template options. It is front-loaded and concise, though a bit brief on error scenarios or prerequisites.

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?

The description covers the basic creation action and templates but lacks mention of return values, error handling, or prerequisites like projectPath validity. Given the tool's moderate complexity and no output schema, it is minimally adequate but not comprehensive.

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 the schema already documents parameters. The description adds value by listing template names and their purposes, but this is marginal. Baseline of 3 is appropriate as description does not significantly enhance parameter understanding.

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?

The description clearly states the tool creates a new GDScript file with optional templates, using specific verbs and identifying the resource. It distinguishes from sibling tools like script-modify (modifies existing scripts) and script-info (queries script info).

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

Usage Guidelines4/5

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

The description indicates to 'use to generate scripts for game logic' and lists available templates, implying this is the creation tool. However, it does not explicitly state when not to use it or mention alternatives like script-modify for modifications.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wvfp/Gear-Godot-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server