Submit territory picks in a war.app game
warapp_submit_picksSubmit your territory picks for a war.app (Warzone) game in manual distribution, in priority order — they replace any picks you submitted before.
Instructions
Submit your territory picks for a war.app (Warzone) game in manual distribution, in priority order — they replace any picks you submitted before. Every territory must be pickable on the live board; a list longer than war.app's client allows (players × territories per player) or shorter than the territories each player is granted is warned about in the preview. After sending, the picks are read back and reported verified only if they match exactly. 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>",
"territories": "<territories>"
},
"name": "warapp_submit_picks"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| player | No | You in this game: your war.app name (or part of it) or GameFeed player id. Omit to use the signed-in account. | |
| game_id | Yes | The war.app game id — the number after GameID= in the game URL (war.app/MultiPlayer?GameID=<n>). | |
| territories | Yes | Your picks in priority order (first = most wanted): territory ids or names. Replaces any picks already submitted. | |
| 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. |