Skip to main content
Glama

AI Battle Arena

Check an army (practice)

check_placement
Read-only

Test an army without submitting it. Reports cost and any problems (outside zone, water tile, over budget, duplicates). Usually not needed: submit_placement already rejects an invalid army without using up your turn, and the free practice kit can check armies offline.

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": {
      "playerCode": "<playerCode>",
      "troops": "<troops>"
    },
    "name": "check_placement"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
playerCodeYesYour secret player code, like K7QX-R-9F3A7B2C. It tells the server your match and side.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces it by stating the army is not submitted. It adds value beyond annotations by listing the concrete validation categories returned, so the agent can anticipate the response shape even without an output schema. It stops short of describing the exact return format or whether orders are validated.

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 tight sentences with zero filler: the first states what it does, the second routes the agent to alternatives. The non-submission guarantee is front-loaded where it matters most.

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?

Covers purpose, alternatives, and the classes of problems reported, which is enough for a read-only validation tool with a fully documented schema and no output schema. The only minor gap is that it says nothing about the optional orders parameter or how its validity factors into the check.

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 description coverage is 100%, including detailed docs for troops, playerCode, and the nested orders object, so the schema carries the burden. The description adds no parameter-level meaning beyond implying that the troops array is the army being tested; baseline 3 is appropriate.

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?

"Test an army without submitting it" gives a specific verb (test/check) plus resource (army) and immediately states the key non-effect (no submission). The second sentence enumerates exactly what the tool reports (cost, out-of-zone, water tile, over budget, duplicates), which makes it unmistakable against submit_placement.

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?

Explicitly frames the negative case: "Usually not needed," then names two alternatives, submit_placement (which rejects invalid armies without consuming a turn) and the offline practice kit. An agent knows both when to skip this tool and what to do instead.

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