Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
observe_stateB

读取玩家可知完整状态。截图可选,会新增本地 PNG;永不改变游戏状态或发送输入。

read_changesA

读取游标之后的变化。无游标或过期自动全量同步;每个 AI 自行保管返回游标。

healthA

检查连接、版本和采集新鲜度;故障以 error 明确返回。

project_cellA

换算当前观测中的可见地图坐标。必须传入该次会话和序号;遮挡、屏幕外、过期均拒绝。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 4 tools

Disambiguation4/5

observe_state and read_changes mostly serve distinct purposes (full snapshot vs. incremental diff), but read_changes can fall back to a full sync when the cursor is missing or expired, creating mild overlap. project_cell and health are clearly distinct from each other and from the observation tools.

Naming Consistency4/5

Three tools follow a consistent verb_noun snake_case pattern (observe_state, read_changes, project_cell), while health breaks the pattern as a standalone noun. The deviation is minor and the overall style remains predictable and readable.

Tool Count5/5

Four tools are well-scoped for an observation-only lens: full state capture, incremental change tracking, health monitoring, and coordinate projection. Each tool earns its place without redundancy or bloat.

Completeness5/5

The set covers the full read-only observation lifecycle: initializing a session via observe_state, polling updates via read_changes, checking connection/version/freshness via health, and translating visible coordinates via project_cell. No obvious gaps exist for the stated purpose, and agents are not left with dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues