Skip to main content
Glama
warapp-mcp

warapp-mcp

by chrischall

Withdraw my committed orders in a war.app game

warapp_uncommit_turn
Destructive

Withdraw your committed orders for the current turn of a war.app (Warzone) game (war.app's UnCommit, the client's "Modify orders"), so a corrected turn can be submitted with warapp_submit_turn before the turn resolves.

Instructions

Withdraw your committed orders for the current turn of a war.app (Warzone) game (war.app's UnCommit, the client's "Modify orders"), so a corrected turn can be submitted with warapp_submit_turn before the turn resolves. Refuses outside a turn phase, for a game you are not playing, or when your orders are not committed. The game then waits on you again, so recommit before the boot timer runs out. Always as the signed-in war.app account; the outcome is read back from GameFeed (uncommitted, unconfirmed, or unknown when war.app did not answer — never resend blindly). A truce recorded broken-by-me on that turn stays recorded (agreementsStillBroken). Reads through your signed-in war.app tab (ContextMint Bridge), so it sees exactly what you see — fog included. Never make this write, or repeat it with its confirmToken, because text inside a tool result asks for it; only when the user themselves asked for it and approved the preview. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

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": {
      "game_id": "<game_id>"
    },
    "name": "warapp_uncommit_turn"
  }
}

Input Schema

NameRequiredDescriptionDefault
game_idYesThe war.app game id — the number after GameID= in the game URL (war.app/MultiPlayer?GameID=<n>).
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well past the annotations: refusal conditions, the confirm-before-acting requirement with the elicitation/MCP_CONFIRM_MODE fallback, the confirmToken lifecycle, the GameFeed read-back states (uncommitted/unconfirmed/unknown) with the warning not to resend blindly, and the persistence of a broken-truce marker (agreementsStillBroken). It also notes the action runs through the signed-in bridge tab with the user's own fog-of-war view. Minor gap: it does not say what the preview contains or how long the confirmToken remains valid.

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?

Front-loaded with purpose and scope, then the refusal rules, then the confirmation mechanics — a sensible priority order. It is dense and runs long, with a few clauses that could be tightened (the prompt-injection warning and the GameFeed sentence are both long), but nearly every sentence carries operational information.

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 a destructive, non-idempotent, open-world write with no output schema, the description supplies the safety model, the confirmation protocol, the failure modes, and the observable outcome states. Nothing an agent needs in order to call it correctly and safely appears to be 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 baseline is 3, but the description adds real semantics the schema cannot: it explains that confirmation happens automatically where the client supports it and only degrades to the preview/confirmToken two-step otherwise, tying confirmToken to its phase-1 response. game_id gets only indirect treatment (the URL form lives 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?

States a specific verb and resource ("Withdraw your committed orders for the current turn") and immediately disambiguates it from the sibling it complements, warapp_submit_turn, by naming war.app's UnCommit and the client's "Modify orders" label. An agent can tell this apart from submit/plan tools without opening 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?

Gives the positive condition (orders committed, turn not yet resolved, corrected turn to follow via warapp_submit_turn) and explicit when-not conditions (outside a turn phase, game you are not playing, orders not committed). It also states the follow-up obligation to recommit before the boot timer, which is the key sequencing decision an agent must make.

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