Skip to main content
Glama

stop_project

Stop the currently running Godot project to halt execution and free system resources.

Instructions

Stop the currently running Godot project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'stop_project' tool. It checks if there is an active Godot process, kills it if present, clears the active process reference, and returns the captured output and errors.
    private async handleStopProject() {
      if (!this.activeProcess) {
        return this.createErrorResponse(
          'No active Godot process to stop.',
          [
            'Use run_project to start a Godot project first',
            'The process may have already terminated',
          ]
        );
      }
    
      this.logDebug('Stopping active Godot process');
      this.activeProcess.process.kill();
      const output = this.activeProcess.output;
      const errors = this.activeProcess.errors;
      this.activeProcess = null;
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(
              {
                message: 'Godot project stopped',
                finalOutput: output,
                finalErrors: errors,
              },
              null,
              2
            ),
          },
        ],
      };
    }
  • The tool definition including name, description, and empty input schema (no parameters required) for the 'stop_project' tool, registered in the ListToolsRequestSchema handler.
    name: 'stop_project',
    description: 'Stop the currently running Godot project',
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
  • src/index.ts:940-941 (registration)
    The dispatch registration in the CallToolRequestSchema switch statement that routes calls to the 'stop_project' tool to the handleStopProject method.
    case 'stop_project':
      return await this.handleStopProject();
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('stop') but lacks behavioral details: it doesn't specify if this is destructive (e.g., terminates without saving), requires specific permissions, has side effects, or what happens on success/failure.

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, direct sentence with no wasted words. It's front-loaded with the core action ('stop') and target, making it highly efficient and easy to parse.

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?

Given the tool's complexity (simple action, 0 params) and lack of annotations/output schema, the description is minimally adequate. It states what the tool does but misses behavioral context (e.g., safety, effects) that would be helpful for a mutation tool with no structured coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of inputs. The description doesn't need to add parameter semantics, and it correctly avoids mentioning any parameters.

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 ('stop') and target ('currently running Godot project'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'run_project' or 'launch_editor', but the verb 'stop' inherently contrasts with 'run' and 'launch'.

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. It doesn't mention prerequisites (e.g., a project must be running), exclusions, or relationships with siblings like 'run_project' or 'get_project_info'.

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/Coding-Solo/godot-mcp'

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