Skip to main content
Glama
TonyBro
by TonyBro

create_game_project

Initialize a new React Three Fiber game project with templates for platformer, puzzle, endless runner, physics-based, or arcade games, and automatically set up Linear integration for project management.

Instructions

Create a new game project with Linear integration and setup

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameNameYesName of the game
gameTypeYesType of game to create
teamIdYesLinear team ID for project creation
projectPathYesPath where to create the game project

Implementation Reference

  • This is the core handler method that orchestrates the creation of a game project, including knowledge updates, Linear integration, and template generation.
    async createProject(args) {
      const { gameName, gameType, teamId, projectPath } = args;
      
      console.log(chalk.blue('\nšŸŽ® Creating game project...\n'));
      
      // Step 1: Update knowledge base
      const knowledgeSpinner = ora('Updating knowledge base...').start();
      try {
        await this.gameTemplateService.updateKnowledge([
          'react-three-fiber',
          'game-design',
          'performance',
        ]);
        knowledgeSpinner.succeed('Knowledge base updated');
      } catch (error) {
        knowledgeSpinner.fail('Failed to update knowledge base');
      }
    
      // Step 2: Create Linear project structure (via MCP tool call)
      const linearSpinner = ora('Creating Linear project...').start();
      let linearProject;
      try {
        linearProject = await this.linearService.createGameDevelopmentStructure(
          teamId,
          gameName,
          gameType
        );
        linearSpinner.succeed('Linear project created successfully');
        
        console.log(chalk.green('\nāœ… Linear project setup complete!'));
        console.log(chalk.yellow(`\nProject: ${linearProject.project.name}`));
        console.log(chalk.yellow(`Sprints: ${linearProject.sprints.length}`));
        console.log(chalk.yellow(`Tasks: ${linearProject.issues.length}`));
      } catch (error) {
        linearSpinner.fail('Failed to create Linear project');
        throw error;
      }
    
      // Step 3: Ask for confirmation to proceed
      const confirmation = await this.askForConfirmation(linearProject);
      
      if (!confirmation.proceed) {
        return {
          status: 'cancelled',
          message: 'Project creation cancelled by user',
          linearProject,
        };
      }
    
      // Step 4: Generate game template
      const templateSpinner = ora('Generating game template...').start();
      let generatedPath;
      try {
        generatedPath = await this.gameTemplateService.generateGameTemplate(
          gameType,
          gameName,
          projectPath
        );
        templateSpinner.succeed('Game template generated');
      } catch (error) {
        templateSpinner.fail('Failed to generate game template');
        throw error;
      }
    
      // Step 5: Create setup instructions
      const setupInstructions = this.generateSetupInstructions(gameName, generatedPath);
    
      return {
        status: 'success',
        message: 'Game project created successfully!',
        linearProject,
        projectPath: generatedPath,
        setupInstructions,
        nextSteps: [
          `cd ${generatedPath}`,
          'npm install',
          'npm run dev',
        ],
      };
    }
  • src/index.js:38-64 (registration)
    Tool registration for 'create_game_project', defining the name, description, and input schema.
    {
      name: 'create_game_project',
      description: 'Create a new game project with Linear integration and setup',
      inputSchema: {
        type: 'object',
        properties: {
          gameName: {
            type: 'string',
            description: 'Name of the game',
          },
          gameType: {
            type: 'string',
            enum: ['platformer', 'puzzle', 'endless-runner', 'physics-based', 'arcade'],
            description: 'Type of game to create',
          },
          teamId: {
            type: 'string',
            description: 'Linear team ID for project creation',
          },
          projectPath: {
            type: 'string',
            description: 'Path where to create the game project',
          },
        },
        required: ['gameName', 'gameType', 'teamId', 'projectPath'],
      },
    },
  • The MCP tool handler method in the main server class that invokes the gameProjectManager service.
    async createGameProject(args) {
      try {
        const result = await this.gameProjectManager.createProject(args);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error creating game project: ${error.message}`,
            },
          ],
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'Linear integration and setup', hinting at external dependencies, but fails to specify critical traits like required permissions, whether the operation is idempotent, potential side effects (e.g., creating files at 'projectPath'), or error handling. For a creation tool with zero annotation coverage, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core action ('Create a new game project') and includes essential context ('with Linear integration and setup') without unnecessary words. Every part earns its place, making it highly concise and well-structured.

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

Completeness2/5

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

Given the complexity of creating a project with external integration, no annotations, and no output schema, the description is incomplete. It omits details on what the tool returns (e.g., success status or project ID), behavioral aspects like error cases, and how it differs from siblings. This leaves gaps for an agent to operate effectively.

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 all four parameters with descriptions and an enum for 'gameType'. The description adds no additional meaning beyond implying that parameters relate to project creation and Linear integration, but it doesn't clarify relationships (e.g., how 'teamId' ties to Linear) or usage nuances, meeting the baseline for high schema coverage.

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 clearly states the action ('Create a new game project') and specifies key features ('with Linear integration and setup'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_game_templates' or 'update_game_knowledge', which would require mentioning it's for initial creation rather than retrieval or modification.

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 provides no guidance on when to use this tool versus alternatives like 'get_game_templates' or 'update_game_knowledge'. It lacks context such as prerequisites (e.g., needing a Linear team ID) or exclusions (e.g., not for updating existing projects), leaving the agent to infer usage based on the tool name alone.

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/TonyBro/MCP_Game'

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