Map Switch
map_switchSet the active campaign map through REST and notify clients over WebSocket, so DMs can switch the table to an existing map by ID. Get IDs from map_list.
Instructions
Set the current campaign map through REST, then notify via WS map.change (DM only). Use map_list to choose an existing map; token_move changes a token, not the active map. REST persistence and WS dispatch are separate: persisted=true does not prove clients received the change. A WS failure returns ok=false with data.persisted=true; do not replay or roll back the saved change. Broadcast receipt remains sent=true, confirmed=false,status="pending"; inspect events_poll for results/errors, not an ACK. Repeating may repeat notifications even when the current map is already correct. v1.5.0 retains the REST-first current-map rule. Returns {ok:true,data} on success; tool-body failures return {ok:false,error} with optional diagnostic data. Argument-schema errors are MCP errors.
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": {
"map_id": "<map_id>"
},
"name": "map_switch"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| map_id | Yes | Existing map ID in the configured campaign, obtained from map_list; becomes the active map for the table. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||