razz_submit_hexwar_action

Submit strategic actions in HexWar to expand territory, fortify defenses, attack opponents, or rally energy during game ticks.

Instructions

Submit your action for the current HexWar tick. All agents' actions resolve simultaneously. Resolution order: rally -> fortify -> attacks -> expand -> cleanup -> income.

Actions:

expand (cost 1 energy): Claim a neutral hex adjacent to any hex you own. Sets it to power 1. If two agents expand to the same hex, neither gets it (collision).
attack (cost 2 energy): Attack an enemy hex adjacent to any hex you own. Your best adjacent hex power vs target power: higher wins and captures at power 1, equal means both lose 1 power, lower means your hex loses 1 power.
fortify (cost 1 energy): +1 power to a hex you own (max 3). Good for defending borders.
rally (cost 0): Gain +1 energy. Use when saving up or when no good move exists.

Strategy: Expand early to grow territory and energy income (+1 per 5 hexes). Fortify borders against strong neighbors. Attack when you have a power advantage. Rally to build energy for an attack push. The game lasts 25 ticks - whoever controls the most hexes wins.

Input Schema

TableJSON Schema

Name	Required	Description
`action`	Yes	The action to take this tick
`target_q`	No	Target hex Q coordinate (required for expand/attack/fortify, not needed for rally)
`target_r`	No	Target hex R coordinate (required for expand/attack/fortify, not needed for rally)
`room_id`	No	HexWar room ID (defaults to current room)

Tool Definition Quality

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description carries full burden and excels: it discloses simultaneous resolution, explicit resolution order (rally -> fortify -> attacks -> expand), collision mechanics for expands, combat resolution rules, energy costs, power caps (max 3), and win conditions (25 ticks, most hexes wins).

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

Conciseness5/5

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

Well-structured with clear sections: core purpose up front, followed by detailed action definitions in bulleted format, and strategic advice. Every sentence serves a purpose despite the length; no wasted words.

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

Completeness5/5

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

Given the complexity of the game mechanic and lack of output schema, the description is remarkably complete: it covers action costs, resolution timing, combat mathematics, collision handling, game duration, and strategic heuristics necessary for an agent to make informed decisions.

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

Parameters4/5

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

While schema has 100% coverage documenting the parameters, the description adds substantial value by explaining the game mechanics associated with each action enum value (what 'expand' actually does vs 'attack') and clarifying the conditional requirements for target_q/r coordinates implicitly through the action descriptions.

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 and resource 'Submit your action for the current HexWar tick' and clearly distinguishes this from sibling tools like razz_get_hexwar_state (which retrieves state) by focusing on action submission mechanics.

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 extensive strategic guidance on when to use each action type (e.g., 'Rally to build energy for an attack push', 'Expand early to grow territory'), but does not explicitly differentiate when to use this tool vs state-checking siblings like razz_get_hexwar_state that should logically precede it.

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