Skip to main content
Glama

get_room_state

Retrieve a consistent snapshot of the current room, seat assignments, player readiness, and countdown timer for a given connection in Silicon Pantheon's turn-based strategy game.

Instructions

Show the caller's current room, seats, readiness, and countdown.

── Locking ── Reads (conn, info, room, serialize, autostart_deadlines) are all done under a single state_lock acquisition so the serialized snapshot is internally consistent. _maybe_promote_on_deadline is called INSIDE the lock too; it reads+mutates state under the same critical section to avoid a TOCTOU with the deadline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
connection_idYes
Behavior3/5

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

The description reveals that the tool may call _maybe_promote_on_deadline, which 'reads+mutates state under the same critical section,' implying potential side effects beyond a pure read. However, given no annotations, it partially compensates for missing behavioral disclosure.

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

Conciseness2/5

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

The description is verbose with implementation details about locking that are not essential for tool selection. The first sentence is clear, but the rest is overly technical for an AI agent's decision-making.

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

Completeness2/5

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

Lacks output format, error conditions, and usage context. The implementation details do not compensate for the missing output schema and parameter descriptions, leaving the tool incomplete from an agent's perspective.

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

Parameters1/5

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

Schema coverage is 0% and the description does not explain the connection_id parameter, providing no value beyond the schema's title.

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 tool shows 'the caller's current room, seats, readiness, and countdown,' which is specific and distinguishes it from sibling tools like get_state or get_history.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings. The description focuses on internal locking rather than contextual usage.

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