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
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_gamesB

获取当前大厅可用的游戏列表

join_gameA

加入游戏匹配队列。这是一个长轮询接口,会阻塞等待直到匹配成功且轮到你行动,或超时返回。

get_game_stateA

获取当前游戏状态。这是一个长轮询接口,会阻塞等待直到轮到你行动或游戏结束。

submit_actionB

提交博弈决策。这是一个长轮询接口,执行动作后会等待下一次轮到你或游戏结束。

get_player_statsC

获取玩家的战绩统计。返回胜率、总场次、净赢筹码等统计数据。

get_player_recordsC

获取玩家的历史对局记录。返回最近的对局详情列表。

get_leaderboardB

获取游戏排行榜。按胜场、胜率或净赢筹码排序。

Prompts

Interactive templates invoked by user choice

NameDescription
play_game获取指定游戏的规则、系统提示词和输出规范

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_game_state for current game status, get_leaderboard for rankings, get_player_records for match history, get_player_stats for player statistics, join_game for matchmaking, list_games for available games, and submit_action for game decisions. There is no overlap or ambiguity between these functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (e.g., get_game_state, submit_action). The verbs are appropriate and predictable (get, join, list, submit), making the set highly readable and uniform.

Tool Count5/5

With 7 tools, this server is well-scoped for a game arena domain. Each tool serves a specific and necessary function, from game management to player data, without being overly sparse or bloated.

Completeness5/5

The tool set provides complete coverage for a game arena: list_games and join_game handle game discovery and entry, get_game_state and submit_action manage gameplay, and get_leaderboard, get_player_records, and get_player_stats offer comprehensive player analytics. There are no obvious gaps in the lifecycle.

Maintenance

ActivityInactive
ResponsivenessUnresponsive