Skip to main content
Glama

project

Search and manage Godot workspaces, inspect file listings and configuration, create new game structures, and set up rules for AI collaboration.

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,钳制上限 10)
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.7)4.7
Behavior2/5

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

annotations 提供 readOnlyHint=false、idempotentHint=false、destructiveHint=false,信号非常弱,描述承担了行为透明化的主要责任。描述虽提到创建项目、设置项目规则等副操作,但未透露 write_config 的写操作,也未说明 setup_project_rules/create_project 可能创建文件(包含 hooks、AGENTS.md、CLAUDE.md 等副作用)。当前描述未与 annotations 矛盾,但行为透明度不足。

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

Conciseness3/5

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

描述以一句紧凑的动词列表呈现,没有无关冗余,做到了简洁。但对一个拥有 9 个 action 和 23 个参数的复杂工具来说,单行列表虽简单但无法承载足够的信息,缺少数层化/分点式结构。

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?

工具复杂度高(9 个 action、23 个参数、嵌套对象),且没有输出 schema,因此描述需要尽可能说明操作和边界,但它只列出部分操作,遗漏 write_config、list_templates、apply_template。没有提及返回格式、副作用或与兄弟工具的取舍关系,整体不够完整。

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?

input schema 对全部 23 个参数都有中文描述,覆盖率为 100%,包括默认值、枚举、示例和特定 action 归属(如 write_config)。因此描述本身无需再重复参数语义;基线 3 合理。描述没有在 schema 之外增加参数含义,但 schema 已足够充分。

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 uses specific verb+resource pairs(搜索、获取、列出、读取、创建、设置,均指向 Godot 项目或项目内容),使代理能够识别这是项目级工具。但它只描述了 6 种动作,遗漏了 action 枚举中的 write_config、list_templates、apply_template,因此区分能力不完全覆盖所有功能。

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?

描述没有说明何时使用该工具而不是使用诸如 scene、script、game、runtime 等兄弟工具。没有提供“不使用此工具”的排除条件或指向替代工具的提示,使用时机只能从项目相关关键词中隐含推断。

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