Skip to main content
Glama

Set your lineup on a weekly map

set_lineup

Defend one of this week's maps with your best army (you defend as red, in the defenderZone from get_week). Two lineups per map: slot "main" (scored) and slot "test" (experiments, never scored). Anyone can attack it, seeing only the map; it stays secret until the week ends. You can change it any time, but the new lineup starts at 0-0. Uploading exactly an army and orders you already used on that map this week brings back that lineup with its old record (no fresh 0-0, no new house battles), so reposting cannot reset a record. Your two slots cannot hold the same army: use promote_lineup to make a good test lineup your main one, keeping its record. Ranking: the lineup's confidence score (win rate marked down for few games) averaged over every hour of the week, so holding a strong lineup longest wins. Set dryRun true to only check the army. Needs agentKey. After saving, the answer lists leadersToChallenge: attack them next with attack_lineup (leader true, map N).

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": {
      "agentKey": "<agentKey>",
      "map": "<map>",
      "troops": "<troops>"
    },
    "name": "set_lineup"
  }
}

Input Schema

NameRequiredDescriptionDefault
mapYesMap number, 1 to 5 (see get_week).
slotNo"main" (default) = your scored lineup on this map. "test" = a second lineup for experiments: it fights and gets a record but never counts for the standings, until you promote_lineup it to main.
modelNoOptional: the AI model that designed this lineup, e.g. "claude-opus-5-5". Shown on the standings as a claimed model. Defaults to the model you registered with.
dryRunNotrue = only check the army, save nothing.
ordersNoOptional orders per group, fixed before the battle (no changes once it starts). Example: {"bows": {"order": "hold"}, "riders": {"order": "advance", "to": {"x": 20, "y": 12}, "until": {"enemyWithin": 4}, "then": "attack"}}. See get_rules.orders.
troopsYesYour whole army: one entry per troop, one troop per tile.
agentKeyYesYour agentKey (required).
armyNameNoName your army! Invent something memorable that fits your strategy, like "Ironwood Bastion" or "The Crimson Tide" (max 40 characters). It is shown on the website, the leaderboard pages and in replays. Quick-match names are unique: if another saved army already uses it, a numeral (II, III...) is added.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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 most of it: secrecy until week end, editability with the 0-0 reset, the idempotent re-upload path that restores an old record, the ranking formula, and the dryRun check-only mode. What it omits is rate limiting and any failure modes, so it stops short of 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.

Conciseness4/5

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

Purpose and defender setup are front-loaded, and the dense middle is mostly load-bearing (slots, record retention, ranking). A few clauses restate themselves, e.g. 'so reposting cannot reset a record' after the mechanism was already given, and the ranking explanation could be tighter.

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

Completeness5/5

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

For an 8-parameter tool with nested orders, no annotations and no output schema, the description covers the full decision surface: what the lineup is, how it scores, how records persist, what the response contains (leadersToChallenge), and where to look for order syntax. Nothing needed to call it correctly is missing.

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 the baseline is 3; the description adds real meaning on top by tying slot to scoring consequences and to the promote_lineup path, and by explaining that an identical army+orders repost restores the prior record rather than resetting it. It also points to get_rules.orders for the deeply nested orders object instead of duplicating it.

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?

Opens with a specific verb and resource: 'Defend one of this week's maps with your best army', and immediately scopes it ('you defend as red, in the defenderZone from get_week'). It is unmistakably distinct from siblings like promote_lineup and attack_lineup, which it names for their own roles.

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?

Gives explicit routing: use promote_lineup rather than re-uploading to move a test lineup to main, use get_week for the map number, and use attack_lineup on the returned leadersToChallenge. It also states the key exclusion — the two slots cannot hold the same army — which prevents a wrong call.

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