Resolve a mission matchup
get_mission_matchupResolves two force dispositions, in the current mission pack or a named one, to the primary mission each side plays (its card: scoring awards, caps, actions, timing), the terrain layouts and deployments for the pairing, and canonical URLs and reference ids for each. Pass each value by id, slug, or name; an unknown or ambiguous value is refused with the valid options. Rules text is withheld: award criteria and card text come back empty, and the textSources of each award names the upstream file and the record id holding its scoring condition, so fetch that file to say what an award scores.
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": {
"yourDisposition": "<yourDisposition>",
"opponentDisposition": "<opponentDisposition>"
},
"name": "get_mission_matchup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| pack | No | Mission pack id or name from list_reference missionPacks. Omit it for the current pack. | |
| llm_model | No | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics. | |
| conversation_id | No | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. | |
| yourDisposition | Yes | Your force disposition, such as Take and Hold. | |
| opponentDisposition | Yes | The opponent’s force disposition. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| you | Yes | ||
| pack | Yes | ||
| terrain | Yes | ||
| opponent | Yes | ||
| revisions | Yes | ||
| attribution | Yes | ||
| deployments | Yes |