battle-arena-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BATTLE_ARENA_URL | No | Base URL of the Battle Arena API | https://battle-arena.manus.space |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_strategiesA | List all available battle strategies (both student-created and example strategies). Returns strategy IDs, names, fighting styles, and sources. |
| get_strategy_codeA | Get the source code of a specific strategy by its ID. Useful for analyzing how a strategy works. |
| run_battleA | Run a 1v1 battle between two strategies. You can specify strategies by ID (from the available list) or provide custom strategy code. Returns the winner, final HP, and total turns. |
| run_tournamentA | Run a round-robin tournament between multiple strategies. All strategies fight each other once. Returns a leaderboard with wins/losses and all match results. |
| get_game_rulesA | Get the game rules and constants (damage values, ranges, stamina costs, grid size, etc.). Useful for understanding the game mechanics when designing strategies. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: rules, strategy code retrieval, listing strategies, single battle, and tournament. No ambiguity.
All tools follow a consistent verb_noun pattern (get_game_rules, get_strategy_code, list_strategies, run_battle, run_tournament).
5 tools is well-scoped for a battle arena server, covering essential actions without unnecessary bloat.
Core battle lifecycle is covered, but missing strategy creation/modification tools and persistent result storage are missing, assuming strategies are externally defined.