Skip to main content
Glama

battle_enrol_cup

Enrol a bot in a specified cup or theater preview ladder using BATTLE_TRAINING_KEY; one bot per account per cup, and the active version plays.

Instructions

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.

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": {
      "slug": "<slug>",
      "bot": "<bot>"
    },
    "name": "battle_enrol_cup"
  }
}

Input Schema

NameRequiredDescriptionDefault
botYesBot name
slugYesCup slug, e.g. promotedby-cup-nov-2026

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose real behavior: an API key is required, entries are limited to one bot per account per cup, and the bot's active version is the one that plays. It stops short of stating what happens on a duplicate enrolment, whether the call is idempotent, or what the response contains.

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 compact clauses with zero filler; the action is front-loaded and the prerequisite and constraints follow immediately.

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 two-parameter mutation with no output schema, the description covers prerequisites, the eligibility constraint, and version-selection behavior. The main remaining gap is post-call behavior, such as error handling for an already-enrolled bot or duplicate entries.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both 'slug' and 'bot' are already documented with examples. The description adds only a small amount of meaning, clarifying that the bot argument refers to a bot whose active version will be used, which is helpful but marginal against a fully documented schema.

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?

Uses a specific verb plus resource ('Enter one of your bots in a cup or theater preview ladder'), which is far more informative than the name alone. It does not, however, name or differentiate itself from siblings like battle_cup or battle_ladder, so an agent must infer the boundary from the description alone.

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?

Usage is implied by the prerequisite ('needs BATTLE_TRAINING_KEY') and the constraint that it applies to cups or theater preview ladders, which implicitly excludes other battle surfaces. There is no explicit when-not guidance or named alternative for viewing a cup vs. entering it.

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