Skip to main content
Glama

battle_create_bot

Creates a bot on your battle.training account from a name, coding agent, and model, requiring BATTLE_TRAINING_KEY and allowing three bots per account.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "agent": "<agent>",
      "model": "<model>"
    },
    "name": "battle_create_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNoThe bot's own X handle, without @
nameYesBot name
agentYesCoding agent id, e.g. claude-code
modelYesModel id, e.g. claude-opus-4-5

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden and does add real value: an auth key requirement and a per-account quota. It stops short of stating side effects (does creating a bot alter ladder/cup eligibility?), what happens on quota exhaustion, or any rate limits, so it is helpful but incomplete for a mutation tool.

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?

Three short sentences, zero filler, with the auth requirement and quota front-loaded before the parameter clarification. Every clause adds information an agent would otherwise have to guess.

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

Completeness3/5

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

There is no output schema, so the description could say what a successful create returns (bot id? handle?), and it omits error behavior at the quota boundary. For a simple 4-param mutation with full schema coverage, the essentials (auth, quota, param meaning) are present, making it adequate but not complete.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema lacks: agent/model are not just IDs but identify the coding agent and model that wrote the controller, clarifying provenance intent. The x parameter is still unexplained in the description, but the schema covers it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a clear verb+resource ('Create a bot on your account') with concrete scope boundaries (BATTLE_TRAINING_KEY required, 3 bots per account). It does not explicitly name a sibling alternative, but the purpose is unambiguous versus read-only siblings like battle_bot.

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

Usage Guidelines3/5

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

It implies when the tool applies by stating prerequisites (needs BATTLE_TRAINING_KEY) and a hard limit (3 bots per account), which an agent can use to decide feasibility. However, it never says when to use this versus other create/upload siblings such as battle_upload_version, and gives no guidance for what to do when the 3-bot cap is hit.

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