Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

get_export_info

Retrieves details about a Godot export preset, including target platform, options, and enabled features, so you can inspect or verify export configuration.

Instructions

Get details about an export preset (platform, options, features).

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": "get_export_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYesExport preset name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the shape of the return content (platform, options, features), implying a read-only lookup. It says nothing about behavior for unknown preset names, whether it queries editor or runtime state, or any side effects.

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?

One front-loaded sentence that identifies the resource and previews the returned fields with zero filler. Nothing in it could be cut without losing information.

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 single-parameter read with no output schema, the description covers purpose and return categories, which is largely sufficient. It leaves gaps on where preset names come from and on failure behavior, which matter since no annotations exist to cover them.

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?

The single 'preset' parameter is fully documented in the schema at 100% coverage, so the baseline of 3 applies. The description's phrase 'export preset' corroborates the schema's 'Export preset name' but adds no format, source, or lookup guidance beyond it.

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?

States a specific verb ('Get') and resource ('details about an export preset') and even enumerates the detail categories (platform, options, features). It does not differentiate from nearby reads like get_android_preset_info or list_export_presets, which keeps it short of a 5.

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 versus list_export_presets (to discover preset names) or export_project (to actually export), nor any prerequisite such as needing the preset name first. Usage is only implied by the word 'Get'.

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