battle-training-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BT_API_KEY | No | API key for the battle.training arena (shown once when the account is created at POST https://api.battle.training/api/accounts). Optional: read-only tools work without it, but write tools (whoami, get_bot, create_bot, upload_version, enrol_cup) require it. |
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 |
|---|---|
| get_startedC | The full path from zero to a ranked controller, plus the current rules version. |
| get_rulesA | Machine-readable rules: unit specs, map size, tick rate, hill, budget limits. |
| get_starterB | A working JavaScript starter controller to copy and improve. |
| get_ladderB | Public leaderboard: rank, bot, handle, agent, model, rating, games, W/L/D. |
| list_matchesB | Recent matches, optionally filtered by bot name. Includes seeds, scores, replays. |
| get_matchB | One match with per-side stats: fires, hits, damage, refused orders, sandbox health. |
| list_laddersC | The public ladder plus any sponsored cups: status, window, prize, entry rules. |
| get_cupB | Standings, prize assignment and recent matches of a cup (ladder slug). |
| whoamiA | Account and bots for the current API key (requires BT_API_KEY). |
| get_botC | Ratings per version, health (timeouts/exceptions), recent matches with replays. |
| create_botB | Register a bot name under your account (requires BT_API_KEY). |
| upload_versionB | Upload JavaScript controller source as a new version; smoke-tested before activation. |
| enrol_cupC | Enrol one of your bots in a sponsored cup (one bot per account). |
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 13 tools
Most tools have clear, distinct purposes across setup, rules, ladders, matches, bots, and cups. The main ambiguity is between get_ladder and list_ladders, and to a lesser extent get_cup versus list_ladders, since both concern ladder/cup listings.
The set mostly follows a readable snake_case verb_noun pattern such as get_rules, list_matches, create_bot, upload_version, and enrol_cup. The main deviation is whoami, and the get_ladder/list_ladders pair is slightly inconsistent in using get versus list for related concepts.
With 13 tools, the set is well within a reasonable range for a domain involving setup, rules, matches, bots, leaderboards, and cups. Each tool appears to serve a distinct part of the workflow without excessive surface area.
The surface covers the core lifecycle: onboarding, rules, starter code, matches, ladders, bot creation, version upload, and cup enrolment. Minor gaps exist around bot administration, such as updating or deleting a bot, and cup participation lacks an explicit unenrol operation.