Skip to main content
Glama

create_room

Create a new game room and become the host. Transition from lobby to active room by specifying a scenario. Configure optional settings for max turns, team assignments, and turn time limits.

Instructions

Create a new room, seating the caller in slot A as the host.

Transitions the caller from IN_LOBBY to IN_ROOM. Fails if the caller isn't IN_LOBBY or already has a room, if the scenario doesn't load, or if the config fields don't validate.

If max_turns is not provided, defaults to whatever the scenario declares in its YAML rules block.

── Locking ── Field validation + scenario load happen OUTSIDE state_lock (pure I/O on YAML). The actual registration (rooms.create + conn_to_room write + conn.state flip + heartbeat_state write) is done atomically under state_lock with a re-check of the caller's state so a concurrent transition can't slip us into a torn state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes
scenarioYes
max_turnsNo
team_assignmentNofixed
host_teamNoblue
fog_of_warNonone
turn_time_limit_sNo
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully discloses behavioral traits: state transitions, locking semantics, default for max_turns, and failure conditions. The detailed locking explanation provides agent-critical context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections and front-loaded main action. It is concise but sufficiently detailed, with no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 parameters, no output schema, and no annotations, the description covers state transitions, locking, and defaults adequately. However, it omits parameter descriptions and return value details, leaving gaps in completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description only explains the max_turns default. It does not describe connection_id, scenario, team_assignment, host_team, fog_of_war, or turn_time_limit_s. The description fails to compensate for the lack of schema-level documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'create' and the resource 'room', specifying that the caller becomes host in slot A. It distinguishes from siblings like join_room and list_rooms by detailing the state transition and failure conditions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is for creating a room, but it does not explicitly state when to use it versus alternatives like create_dev_game or join_room. No guidance on prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/haoyifan/Silicon-Pantheon'

If you have feedback or need assistance with the MCP directory API, please join our Discord server