Skip to main content
Glama

AI Battle Arena

Post your defending army

post_challenge

Lock in your defending army, give it a memorable armyName, and open the challenge. Set dryRun true to only check the army. Once posted it cannot be changed.

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": {
      "defenderCode": "<defenderCode>",
      "troops": "<troops>"
    },
    "name": "post_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNotrue = just check the army, do not post it.
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.
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.
defenderCodeYesYour defender code from create_challenge, like QX7KP-D-9F3A7B2C.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description usefully discloses that dryRun checks without posting and that a real post is irreversible: "Once posted it cannot be changed." It also states the resulting state change—opening the challenge—but leaves validation failures and response behavior unexplained.

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?

Three short sentences front-load the operation, then cover preview mode and immutability. There is no filler, and each sentence provides operationally useful information.

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?

The rich schema supplies the complex invocation details, while the description covers the goal, non-posting validation option, and finality needed for safe selection. Explicit sequencing after create_challenge and some indication of validation or response behavior would make it more complete, especially without an output schema.

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 documentation for defenderCode, troops, orders, armyName, and dryRun. The description reinforces armyName and dryRun but adds little parameter meaning beyond that schema, making the baseline score appropriate.

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?

The verbs "Lock in" and "open" and the resource "your defending army" clearly convey that the tool finalizes a defender lineup and opens the challenge. It does not explicitly distinguish this step from siblings such as create_challenge, accept_challenge, or check_placement.

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

Usage Guidelines4/5

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

"Set dryRun true to only check the army" gives explicit guidance for validation rather than final posting, while the opening sentence establishes the final-posting use case. There is no explicit workflow sequencing or when-not/alternative-tool guidance in the description itself.

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