galgame-mcp-engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GALGAME_DIR | Yes | Path to the .game directory containing save files |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| galgame_startA | 启动或恢复 Galgame 世界引擎。返回完整世界状态上下文（角色全档案+关系+时间线+谜团+位置+物品）。 |
| galgame_actionB | 提交一轮玩家操作。choice: A/B/C/自由文本。narrative: 完整四段叙事。引擎校验格式后更新存档并返回下一幕上下文。 |
| galgame_statusB | 获取世界状态的口吻式摘要。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: starting the game, submitting actions, and getting status. No overlap or confusion.
All tools follow the 'galgame_' prefix with a clear verb (start, action, status), consistent snake_case pattern.
Three tools is appropriate for a galgame engine MCP, covering initialization, interaction, and state summary without bloat.
Covers core game loop well, but lacks an explicit save/load tool (though start handles recovery). Minor gap.