Skip to main content
Glama

project

Search, inspect, create, and configure Godot projects. List files, read/write configs, and set up project rules for AI-assisted workflows.

Instructions

搜索 Godot 项目、获取项目信息、列出文件、读取配置、创建项目、设置项目规则。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ciNo生成 GitHub Actions CI workflow(默认 false)
keyNo配置键(write_config,如 "application/config/name")
tagNo模板:按标签过滤
forceNo覆盖已有配置(默认 false)
hooksNo创建 .claude/settings.json 的 PostToolUse hook(默认 true)
valueNo配置值(write_config)
actionYes操作类型
rendererNo渲染器:"forward_plus"(默认)、"mobile"、"gl_compatibility"forward_plus
templateNo项目脚手架模板:2d-platformer / 3d-fps / visual-novel(默认空)
agents_mdNo创建/追加 AGENTS.md 项目规则(ZCode/Codex/Cursor 等遵循 AGENTS.md 标准的客户端读取,默认 true)
claude_mdNo创建/追加 CLAUDE.md 验证规则(默认 true)
max_depthNo最大搜索深度(默认 3)
variablesNo模板:变量覆盖
applies_toNo模板:按适用类过滤
extensionsNo按扩展名过滤(如 [".gd", ".tscn"])
rules_modeNo规则文件 reconcile 模式:check(默认,只检测报告)/ update(覆盖版本过时且未动过的文件,保留用户动过的)/ overwrite(全覆盖含本地修改)check
search_dirNo搜索目录(list_projects).
script_pathNo模板:目标脚本路径
template_idNo模板:模板 ID(如 T008)
project_nameNo项目名称(默认取文件夹名)
project_pathNoGodot 项目目录路径(可选,默认使用 GODOT_PROJECT_PATH 环境变量或当前目录)
subdirectoryNo限定子目录
godot_versionNoCI 中使用的 Godot 版本(默认 4.4)4.4
Behavior2/5

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

Annotations are minimal (all false), and the description adds no behavioral context. It does not mention side effects of mutating actions like create_project, write_config (with force), or setup_project_rules which may overwrite files. The description offers no warnings or clarifications about destructive potential or required permissions.

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 sentence listing six actions, which is concise and free of unnecessary words. However, it is a comma-separated list lacking structure or emphasis, and it omits three actions, making it slightly incomplete but still efficient.

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?

Given the tool's complexity (23 parameters, 9 actions, no output schema), the description is far from complete. It covers only six of nine actions and provides no information about return formats, error handling, environment variables, or typical workflows. The high schema coverage mitigates this partially, but the description itself is insufficient.

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 description adds no parameter-level details, but the input schema provides full coverage (100%) with descriptive comments for each parameter, including defaults and enums. This meets the baseline for schema-heavy descriptions, but the description itself does not enhance understanding of parameter usage.

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 clearly states the tool performs multiple project-related operations: searching Godot projects, getting project info, listing files, reading configuration, creating projects, and setting project rules. It distinguishes itself from sibling tools by focusing on project-level management, though it omits some actions like write_config and template application.

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 is provided on when to use this tool over alternatives. The description merely lists capabilities without explaining appropriate contexts, prerequisites, or exclusions. For example, it does not clarify when to use write_config versus other configuration tools.

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