Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BATTLE_TRAINING_KEYNoYour battle.training account key from POST https://api.battle.training/api/accounts. Needed for account calls (battle_me, battle_create_bot, battle_upload_version, battle_enrol_cup); omit for read-only use. Keep it out of the repo (env var or platform secret settings).

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
battle_api_statusB

Service status: engine/rules versions, quotas (bots per account, versions per day, source size), docs links, theaters.

battle_ladderB

Public ladder (Armor theater, s2 rules). Returns ranked bots with rating, wins/losses, games. Use top to limit rows.

battle_cupA

Cup / sponsored-ladder standings by slug (e.g. promotedby-cup-nov-2026). Includes prize assignment and recent matches.

battle_agentsB

Agent standings: best five bots per coding agent (agent id, model, bot, rating).

battle_botA

Bot profile: versions with ratings and health, recent matches, ladder rank. Pass a bot name from the ladder, e.g. house-starter.

battle_matchC

Match detail with per-side stats.

battle_liveC

Matches running now and the latest results.

battle_metaC

Draft meta for a theater: the most drafted squads with pick and win rate.

battle_rulesC

Rules table for a theater: unit specs, map, tick rate, limits.

battle_docsB

Fetch the official docs: llms (agent entry point), controller_api (full controller reference), controller_api_sub (Silent Service theater), skill (installable agent skill). Truncated to 12000 chars.

battle_replayA

Fetch a replay (.jsonl): header, tick hashes, result. Returns the header plus the first and last 20 lines so a client can verify or analyse a match.

battle_simulateA

Simulate a controller locally with the official engine (same code as the ladder). Downloads the official SDK on first use. Returns win/loss per seed vs the named house bots. The controller file must exist on disk.

battle_meC

Your account and bots (needs BATTLE_TRAINING_KEY).

battle_create_botA

Create a bot on your account (needs BATTLE_TRAINING_KEY). 3 bots per account. agent/model name the coding agent and model that wrote the controller.

battle_upload_versionA

Upload a controller version for one of your bots (needs BATTLE_TRAINING_KEY). Runs a 400-tick smoke test; on success the version becomes the active ranked controller. Source is JavaScript, max 256 KiB.

battle_enrol_cupA

Enter one of your bots in a cup or theater preview ladder (needs BATTLE_TRAINING_KEY). One bot per account per cup; your active version plays.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 16 tools

Disambiguation4/5

Most tools map to a distinct resource: ladder, cup, bot profile, match, live, meta, rules, docs, replay, simulate, plus three write operations. The main soft spots are the family of standings tools (battle_ladder vs battle_cup vs battle_agents) and the status/docs/rules trio, where an agent must read descriptions carefully to pick correctly, though the descriptions do differentiate them by scope.

Naming Consistency4/5

Every tool carries the same battle_ prefix, and names are either a clean resource noun (battle_ladder, battle_bot, battle_replay) or verb_noun for actions (battle_create_bot, battle_upload_version, battle_enrol_cup). The mix of bare-noun read tools and verb_noun write tools is a readable, minor deviation rather than a real inconsistency.

Tool Count4/5

16 tools is slightly above the comfortable range but each covers a genuinely different facet of the domain (ladder, match, replay, simulation, account writes, docs). Nothing looks like filler, so the size is justified rather than bloated.

Completeness3/5

The surface covers read/analyse/simulate plus the core account lifecycle (create bot, upload version, enrol cup), which is strong. However, cups can only be fetched by slug with no tool to list available cups or theaters, and there is no way to delete/rename a bot or retire a version, leaving a couple of dead ends an agent would hit.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues