Skip to main content
Glama
xinyuzjj

Godot MCP Enhanced

by xinyuzjj

stop_project

Halt the currently running Godot project.

Instructions

Stop the currently running Godot project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that stops the currently running Godot project. It kills the active process via process.kill() and clears the activeProcess reference.
    private async handleStopProject(): Promise<ToolResult> {
      if (!this.activeProcess) {
        return this.createErrorResponse('No active Godot process to stop.');
      }
    
      this.logDebug('Stopping active Godot process');
      this.activeProcess.process.kill();
      this.activeProcess = null;
    
      return this.createSuccessResponse('Godot process stopped successfully.');
    }
  • src/index.ts:503-511 (registration)
    Tool registration for 'stop_project' in the tools list with name, description, and empty inputSchema.
    {
      name: 'stop_project',
      description: 'Stop the currently running Godot project',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:793-795 (registration)
    Case branch in the tool request handler that dispatches to handleStopProject() when the tool name is 'stop_project'.
    case 'stop_project':
      result = await this.handleStopProject();
      break;
Behavior2/5

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

Description only says 'Stop the currently running Godot project' with no details on side effects (e.g., unsaved changes), multiple calls, or error states. Annotations are absent, so description should compensate but does not.

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?

Single sentence, concise, no wasted words. Front-loaded with the action and target.

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 simple action with no parameters and no output schema, the description is adequate but lacks context on what 'currently running' means (e.g., which project instance) and possible error conditions. Could be more complete.

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?

Input schema has zero parameters and 100% coverage from schema. Description does not need to add parameter info. Baseline for 0 params is 4, and no additional value is missing.

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?

Description clearly states 'Stop the currently running Godot project', specifying the verb 'stop' and the resource 'currently running Godot project'. It distinguishes from sibling 'run_project' which starts a project.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, conditions, or when not to call it, despite the presence of sibling tools like 'run_project'.

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

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