Skip to main content
Glama

create_project

Creates a Godot 4 project under the projects directory with scenes/ and scripts/ folders and a Node2D main scene, giving you a ready structure for game development.

Instructions

Create a Godot 4 project with a scenes/ and scripts/ folder and a main scene (scenes/main.tscn, Node2D root). Creates the project under the projects directory.

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

Input Schema

NameRequiredDescriptionDefault
nameYesProject folder name (letters, digits, . _ -)
display_nameNoGame title shown in Godot; defaults to name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden and does disclose meaningful side effects: the folder structure, main scene path, Node2D root, and projects-directory location. However, it omits important behavior such as handling of an existing project name, overwrite/conflict behavior, permissions, and failure outcomes.

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?

The description is two sentences, front-loaded with the core action, and every clause adds useful information about what gets created or where. There is no redundant or filler wording.

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 project-creation tool with no annotations and no output schema, the description covers the main created artifacts and location but leaves key create-operation context unspecified. An agent would still not know what happens if the project already exists or what the tool returns or guarantees after creation.

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 both name and display_name, including the default for display_name and the allowed name characters. The description adds the target projects directory and generated structure, but does not add meaning beyond the schema for the parameters themselves.

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 Godot 4 project. It also specifies the generated folders and main scene, which makes the project-level operation distinguishable from scene- or script-level siblings, though it does not name those siblings explicitly.

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?

The description does not say when to use this tool versus alternatives such as validate_project, create_scene, or create_script. Usage is only implied by the verb 'Create', with no explicit preconditions, exclusions, or alternative routing.

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