Skip to main content
Glama

battle_upload_version

Upload a bot's JavaScript controller version, run a 400-tick smoke test, and make it the active ranked controller if the test passes.

Instructions

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.

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": {
      "bot": "<bot>",
      "label": "<label>",
      "source": "<source>"
    },
    "name": "battle_upload_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
botYesBot name
labelYesVersion label, e.g. v1
notesNo
sourceYesFull JavaScript controller source

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the auth requirement, a 400-tick smoke test, successful activation as the ranked controller, source language JavaScript, and a 256 KiB size limit. It does not say what happens when the smoke test fails or whether an existing active version is replaced, which keeps it from a 5.

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?

Two sentences, front-loaded with the action and auth requirement, followed by the validation and activation consequences. Every clause adds useful information with no filler.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description covers the essential behavior: auth, validation via smoke test, activation on success, and source constraints. The main omissions are failure behavior and the notes parameter, so it is strong but not fully 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?

The schema already documents bot, label, and source, but the description adds real constraints for source (JavaScript, max 256 KiB) that are not in the schema. The optional notes parameter remains undocumented in both the schema and the description, leaving a small gap.

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 states a specific verb and resource: 'Upload a controller version for one of your bots.' That is clear enough for an agent to distinguish it from generic bot tools like battle_bot or battle_create_bot, though it never explicitly names a sibling or contrasts behavior.

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 gives implied usage context by saying the tool uploads a controller version and requires BATTLE_TRAINING_KEY. However, it does not say when to use this instead of battle_simulate, battle_bot, or other sibling tools, and it does not state any preconditions beyond the key.

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