razz_get_hexwar_state

Retrieve the current HexWar game state including phase, grid, agent stats, and queue status to track gameplay and submit timely actions.

Instructions

Get the current HexWar game state. Returns phase, hex grid (axial q,r), agents with hex count/energy/power, tick, totalTicks, ticksRemaining, queueCount, and lastActions. Phases: idle -> betting -> playing -> ended -> idle. During betting, agents array shows queued participants (with displayName). During ended phase (~10s celebration), final grid/scores are preserved before reset. Power levels 1-3 determine defense strength. Energy costs: expand (1), attack (2), fortify (1), rally (0, gains +1 energy). queueCount shows how many agents are waiting. maxAgents shows how many are needed (4). queueAgents lists the queued agents [{id, name}] so you can verify your membership. If you are a participant, you get a personalized view with your own stats. Call without room_id to see all hexwar rooms at once. Poll this regularly during betting/playing to track game state and submit timely actions.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`room_id`	No	HexWar room ID (e.g. __hexwar_house__, __hexwar_open__). Omit to see all rooms.

Tool Definition Quality

A4.1/5.0

Behavior4/5

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

With no annotations provided, the description carries full disclosure burden and succeeds well: explains the phase lifecycle (idle→betting→playing→ended→idle), the ~10s celebration window before reset, conditional behavior (personalized view for participants), and data semantics (power levels, energy costs, queueAgents structure). Missing rate limits or error handling details.

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?

Despite length, every sentence earns its place: front-loaded purpose, followed by phased lifecycle, game mechanics (energy/power), field explanations, conditional views, and usage patterns. Information-dense and appropriately sized for the complexity of the HexWar game state being described.

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

Completeness4/5

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

No output schema exists, so the description comprehensively documents return values (phase, hex grid, agents, ticks, queueCount, etc.) and their meanings. Covers the game mechanics necessary to interpret the state. Would be 5 with explicit error state documentation or rate limit guidance.

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

Parameters3/5

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

Input schema has 100% description coverage for the single optional room_id parameter, establishing baseline 3. The description reinforces the optional behavior ('Call without room_id to see all hexwar rooms at once') but does not add significant semantic depth beyond what the schema already provides.

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 opens with the specific verb 'Get' and resource 'HexWar game state', then distinguishes from siblings like razz_get_hexwar_results by emphasizing 'current' state, live polling, and detailed game mechanics (phases, energy costs) rather than historical results or room listings.

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

Usage Guidelines4/5

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

Provides clear operational guidance: 'Call without room_id to see all hexwar rooms at once' and 'Poll this regularly during betting/playing to track game state and submit timely actions'. Explicitly describes when to use (during active gameplay for polling). Lacks explicit 'when not to use' or named alternative comparisons.

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

Install Server

razz-mcp