Skip to main content
Glama

runtime

Launch Godot editor, run or stop projects, retrieve debug output, run tests, and get the Godot version.

Instructions

启动编辑器、运行/停止项目、获取调试输出、运行测试、获取 Godot 版本。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
speedNo录制:回放速度倍率(默认 1.0)
actionYes操作类型
timeoutNo自动停止秒数(默认 30)
file_nameNo录制保存:始终自动命名 recording_YYYYMMDD_HHmmss.json(file_name 入参被忽略);但 file_name 须匹配 recording_*.json 格式(否则 INVALID_FILE_NAME),禁止含 / \\ ..
godot_pathNo覆盖 Godot 二进制路径(可选,优先于项目配置和环境变量)
events_jsonNo录制:JSON 格式的事件序列字符串
test_scriptNo测试脚本或目录路径(默认 res://test/)res://test/
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
bridge_timeoutNowait_for_bridge 轮询总预算(秒,默认 10)
load_autoloadsNo是否加载 Autoload 上下文(默认 true)
wait_for_bridgeNotrue 时 spawn 后轮询 bridge 就绪(默认 false,向后兼容)
Behavior2/5

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

The description lists basic operations but does not elaborate on side effects (e.g., stopping a project may terminate processes, running tests may write files). With all annotations false, the description was expected to add behavioral context but only names the actions without caveats.

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?

The description is a single concise sentence listing the main actions. It is efficient and readable, though it misses some schema actions like the recording set.

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?

The tool supports 11 actions, but the description covers only 5, omitting the recording-related actions (record_start, record_stop, etc.). No output behavior is described, and there is no output schema to compensate. This is insufficient for a multi-action tool.

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?

All 11 parameters have schema descriptions with 100% coverage, so the description does not need to explain parameters. It adds no additional semantic meaning beyond the schema, matching the baseline.

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 lists specific actions (launch editor, run/stop project, get debug output, run tests, get Godot version) that clearly define the tool's scope. However, it does not differentiate this tool from siblings like 'editor' or 'project', and it omits the recording actions present in the schema.

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 usage guidance is provided. The description gives no context about when to use this tool versus the numerous sibling tools, nor any prerequisites or exclusions.

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

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