shapez 1 游玩 MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHAPEZ_MODE | No | Set to "observe" to only observe the game without write access. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusB | 查看当前活动存档、关卡、世界规模、视野和可用能力。 |
| entitiesA | 查询建筑分组或冻结明细。region 为半开 tile 区间,摘要的 firstCursor 用于同一视图的分页。 |
| resourcesC | 查询资源斑块。用 color:green 或 shape:CuCuCuCu 等规范键筛选。 |
| sample_flowB | 在时间窗内多次采样指定区域的物流与交付进度,返回序列与增量。 |
| screenshotA | 截取当前存档的游戏画面与 HUD,返回 PNG 图像。窗口不可见时会失败。 |
| preview_beltsA | 预演直带施工:返回每格前后状态与邻格影响,不改变现场,计划 60 秒有效。 |
| apply_beltsA | 提交已预演的计划并留存快照,返回携带快照编号的回执。 |
| operation_statusB | 按请求键查询施工或恢复回执。 |
| restore_snapshotB | 按快照编号与原施工请求键恢复施工前现场。 |
| gameC | select(id=活动档 internalId) 绑定写入;layer 切 E 视角;trace(at) 查上游堵点;check_signals(tiles,reference 或 network,pin,value) 只报异常;hub/speeds/catalog/building/path/flow 查询;place(items)/remove(tiles 或 region)/route(route)/wire(route,color,join)/blueprint(capture 或 paste)/configure/upgrade。坐标 [x,y]。 |
| map_regionB | 完整局部地图。region=[x0,y0,x1,y1] 右下不含,最多 32×32,format=rows/image,layer=regular/wires/both。 |
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 11 tools
Most dedicated tools (status, entities, resources, screenshot, map_region, preview_belts, apply_belts, operation_status, restore_snapshot) have reasonably distinct purposes, but the 'game' tool is an overloaded mega-tool whose many query and mutation subcommands overlap with several of those dedicated tools. Agents may struggle to decide when to use 'game' versus 'entities', 'resources', 'sample_flow', or 'map_region', creating unclear boundaries.
All names use snake_case and are readable, but the naming pattern is mixed: some are bare nouns (status, entities, resources, game), some are verb_noun (sample_flow, preview_belts, apply_belts, restore_snapshot), and some are noun phrases (map_region, operation_status). There is no predictable verb or noun convention across the set.
Eleven tools is a reasonable raw count, but the 'game' tool bundles dozens of distinct operations into one entry, so the effective surface is much larger than the count suggests. The count under-represents the domain and hides complexity inside a single catch-all tool.
The set covers inspection, construction preview, apply, snapshot restore, operation receipts, signal checks, and several query modes, giving solid lifecycle coverage for a shapez automation server. Minor gaps such as explicit cancellation or broader save/load management may exist, but core workflows appear workable.