Skip to main content
Glama

Start my tournament battle

start_event_battle
Destructive

Starts the battle for a revealed tournament or hidden-list game with both sealed lists attached, as Start battle on its page does, and returns its token for get_my_battle and submit_battle_action. In Swiss rounds omit opponentId to play your current table; Swiss refuses anyone else. Otherwise name the opponent from get_my_event's entrants, and for a team game the ally and second opponent too. For a league with sealed lists, pass the fixtureKey, token and opponentId from get_my_group. Requires mcp:write.

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": {
      "token": "<token>"
    },
    "name": "start_event_battle"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesThe tournament or hidden-list game token, from list_my_events or its invite link.
allyIdNoYour ally in a 2v1 or 2v2 game.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
eventTokenNoeventToken from list_my_events; only an old link needs it.
fixtureKeyNoThe sealed league fixture key from get_my_group.
opponentIdNoAn entrant id; omit in Swiss rounds for your paired opponent.
missionPackIdNoA mission pack id from list_reference; omit for the current pack, as the site does.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
secondOpponentIdNoThe second opposing player in a 2v1 or 2v2 game.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fixtureKey
      Added value: +{
      +  "description": "The sealed league fixture key from get_my_group.",
      +  "maxLength": 256,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / conversation_id
      Added value: +{
      +  "description": "The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The model identifier you are running as, for example \"claude-opus-4-8\" or \"gpt-5.2\". Pass \"unknown\" if you are not certain. Recorded for the server developer's analytics.",
      +  "type": "string"
      +}
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations it discloses the auth requirement ('Requires mcp:write'), the fact that it is equivalent to pressing Start battle on the page, and a behavioral rule (Swiss refuses a named opponent). It does not explain the destructiveHint=true consequence — e.g. what state is consumed or whether a battle can be restarted — which is the biggest remaining gap 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and return value are front-loaded, then usage is layered by format in a logical order with no filler sentences. It is a dense single paragraph, and splitting the format branches would slightly aid scanning, but nothing is wasted.

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 9-parameter mutation with an open-world, non-idempotent profile and no output schema, the description covers entry conditions, per-format parameter sourcing, and the returned token's downstream use. It falls short on failure behavior — what happens if the battle is already started, the round isn't paired, or the caller lacks mcp:write — which an agent would need to handle errors.

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 already 100%, so the baseline is 3, but the description adds real decision-level meaning: which parameters apply in Swiss vs. non-Swiss vs. team vs. sealed-league fixtures, and where each id comes from (get_my_event, get_my_group). It does not cover eventToken, missionPackId, or the analytics-only fields, but those are self-documented in the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Starts the battle for a revealed tournament or hidden-list game'), scopes it to games with sealed lists attached, and states the returned token feeds get_my_battle and submit_battle_action. That distinguishes it from siblings like create_battle or start_sealed_league without the agent needing to open a schema.

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

Usage Guidelines5/5

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

It gives explicit mode-by-mode selection rules: in Swiss rounds omit opponentId and 'Swiss refuses anyone else', otherwise name the opponent from get_my_event's entrants, add ally and second opponent for team games, and use fixtureKey/token/opponentId from get_my_group for a sealed league. When-to-use and when-not-to-use are both covered with the sibling each value comes from.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources