Skip to main content
Glama
lonexreb

gap

by lonexreb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

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
list_gamesA

List available games (with action grammar), active tables, and their open seats.

resetA

Start a fresh game on a table and return the initial observation.

table names the session so several games can run concurrently (defaults to
the game name). Solo play: just call act() next. Multi-agent play: each
agent calls join() to claim a seat, then loops wait_turn() -> act().
joinA

Claim a seat at a table (a specific one, or the next open one).

Returns your secret seat_token — pass it to wait_turn/observe/act. Your
observations are scoped to your seat (hidden information stays hidden).
observeB

Current observation for a table — seat-scoped if you pass your seat_token.

actA

Play one action (must be in your legal_actions). Returns your new observation.

On a table with claimed seats you must pass your seat_token, and it must be
your turn.
wait_turnA

Block until it is your seat's turn (or the game ends, or timeout).

On timeout the observation comes back with your_turn=false — just call
wait_turn again. Keep timeout_s below your client's tool timeout.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool targets a distinct operation: reset starts a game, join claims a seat, observe reads state, act changes state, wait_turn blocks for turn changes, and list_games enumerates available games and tables. There is no meaningful overlap or ambiguity between their purposes.

Naming Consistency4/5

Tool names are all lowercase imperative verbs, with compound names using snake_case (wait_turn, list_games). The style is consistent and readable, though bare verbs like act and observe are less descriptive than verb_noun patterns.

Tool Count5/5

Six tools form a well-scoped set for a game-session server: setup, joining, turn handling, acting, observing, and discovery. Nothing feels redundant or missing at the count level.

Completeness4/5

The core game lifecycle is covered: create/start, join, observe, act, wait, and list. Minor gaps exist such as no explicit leave/seat-release or table-close operation, but agents can work around them using the available surface.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources