Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

export_project

Export a Godot project using a named export preset, with optional output path and debug build settings, to produce a distributable game build.

Instructions

Export the project using a named export preset.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOutput path for the exported build
debugNoExport as debug build
presetYesExport preset name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing. It does not say whether the export is long-running or blocking, whether writing to an existing path overwrites files, what happens if the preset name is invalid, or whether the build output is reported back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

A single front-loaded sentence with no wasted wording. It is efficient, but the brevity is achieved by omitting information rather than by tight phrasing of complete information.

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?

This is a mutation/expensive operation with no annotations, no output schema, and no explanation of results, side effects, or failure modes. For a three-parameter export action, the description is too thin to let an agent invoke it confidently.

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 explains preset, path, and debug; the baseline of 3 applies. The description adds only marginal meaning by implying the preset must be an existing named preset, and says nothing about path or debug behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb+resource ("Export the project") and adds the mechanism ("using a named export preset"), which is more than a bare restatement of the name. However, it does not distinguish this from siblings such as list_export_presets or get_export_info, leaving the agent to infer the boundary.

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 when-to-use guidance at all: nothing says when to prefer this over list_export_presets (to discover preset names) or get_export_info (to inspect results). The only implied prerequisite is that a preset name must already be known, and even that is not stated.

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

Deploy Server

Other Tools