Withdraw my committed orders in a war.app game
warapp_uncommit_turnWithdraw 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
| Name | Required | Description | Default |
|---|---|---|---|
| game_id | Yes | The war.app game id — the number after GameID= in the game URL (war.app/MultiPlayer?GameID=<n>). | |
| confirmToken | No | ONLY 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. |