Skip to main content
Glama

battle_simulate

Simulate a local controller against named house bots with the official ladder engine; get per-seed win/loss results from an existing controller .js file.

Instructions

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.

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": {
      "controller": "<controller>"
    },
    "name": "battle_simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNoComma-separated house bots to play againstbrawler,holder,random,hunter
rulesNos2
seedsNoNumber of seeds to test
controllerYesPath to a controller .js file

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, the description carries the full burden and does well: it discloses a side effect (SDK download on first use), a filesystem precondition (controller must exist on disk), and the return shape (win/loss per seed per house bot). It omits runtime expectations and whether anything is uploaded or authenticated.

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?

Four short sentences, front-loaded with the core action, then side effects, then return value, then precondition. Every sentence adds information and nothing is redundant.

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?

Return values and preconditions are covered, which matters given no output schema and no annotations. The remaining gap is the undocumented 'rules' mode parameter, which an agent cannot select confidently without knowing what s2/s1/sub mean.

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?

At 75% schema coverage the schema already documents three params, and the description reinforces 'vs' (named house bots), 'seeds' (per seed) and the controller disk requirement. The 'rules' enum (s2/s1/sub) is documented in neither the schema description nor the description, leaving one parameter unexplained.

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?

Specific verb ('Simulate') plus resource ('a controller locally with the official engine'), and it distinguishes the run mode from the ladder by stating it uses 'same code as the ladder' but runs locally. It never names a sibling tool explicitly, so disambiguation relies on inference rather than routing.

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: 'controller file must exist on disk' plus 'same code as the ladder' suggests pre-submission local testing. There is no explicit when-to-use/when-not statement and no pointer to an alternative such as battle_bot or battle_ladder for server-side runs.

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