Skip to main content
Glama
xinyuzjj

Godot MCP Enhanced

by xinyuzjj

get_godot_version

Retrieves the installed Godot editor version to verify your development environment.

Instructions

Get the installed Godot version

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'get_godot_version' tool logic. It checks for a valid Godot path, runs 'godot --version', and returns the version string.
    private async handleGetGodotVersion(): Promise<ToolResult> {
      try {
        if (!this.godotPath) {
          await this.detectGodotPath();
        }
    
        if (!this.godotPath) {
          return this.createErrorResponse('Could not find a valid Godot executable.');
        }
    
        const { stdout } = await execFileAsync(this.godotPath, ['--version']);
        return this.createSuccessResponse(`Godot version: ${stdout.trim()}`);
      } catch (error: unknown) {
        const errorMessage = error instanceof Error ? error.message : 'Unknown error';
        return this.createErrorResponse(`Failed to get Godot version: ${errorMessage}`);
      }
    }
  • The tool definition and schema registration. The tool takes no arguments (empty inputSchema).
    {
      name: 'get_godot_version',
      description: 'Get the installed Godot version',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • src/index.ts:796-798 (registration)
    The switch-case where the tool name 'get_godot_version' is routed to the handler handleGetGodotVersion().
    case 'get_godot_version':
      result = await this.handleGetGodotVersion();
      break;
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. It does not disclose that the tool is read-only and non-destructive. While the name implies safety, explicit mention of no side effects would be beneficial.

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?

A single, front-loaded sentence with zero wasted words. Every word earns its place.

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

Completeness4/5

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

Given zero parameters, no output schema, and a simple purpose, the description is mostly complete. It could be improved by mentioning the return type (e.g., 'returns a version string'), but it adequately conveys the tool's function.

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 input schema has zero parameters and 100% schema description coverage. The description adds no parameter information (none needed). Baseline is 4 because there is no gap to compensate.

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 'Get the installed Godot version' uses a specific verb ('Get') and resource ('installed Godot version'), clearly distinguishing it from all sibling tools which deal with nodes, scripts, scenes, projects, etc.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. However, given the tool's unique purpose (version retrieval) and no competing tools, usage context is implied. A statement like 'Use this to check the engine version before project operations' would improve it.

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