analyze_game_log
Replay a pasted duels.ink game log turn by turn to see why you won or lost, and get concrete tips for your next match based on your deck list.
Instructions
Review a finished (or conceded) duels.ink game from its pasted game log: what happened turn by turn, why the game was won or lost, and concrete tips for next time.
How the player gets the log: in duels.ink, open the in-game log panel and
copy all of it. Paste it as log exactly as copied. It works with one
event per line or with everything run together on one line (some copies
lose the line breaks). "You" in the log is the player asking.
What it does: replays the log to track lore, ink, your hand (you see your own draws), both boards and every banish with its cause. It undoes any "free undo" steps first. Reports:
result, turns, on the play/draw, mulligans;
a per-turn table of your ink, plays (ink paid vs. available), songs, quests and the lore race;
the opponent's inks, cards seen, and the closest known tournament list (from get_meta's bundled decklists, same inks only);
key moments (multi-kill turns, top opposing questers);
tips: damage-sweeper exposure, board collapses to challenges, questing into a challenge, threats left alive too long, missed ink, unspent ink, ink choice, losing challenges, slow starts.
Deck-specific tips need the player's deck. Pass it as deck_list
("4x Card Name" per line, the duels.ink import format) or deck_path (a
file containing such a list, e.g. a deck .md with a duels.ink import
block; the last such block is used). If neither is given and you don't
already know which deck the player was on, ask them which deck they
played before (or after) calling this, since the deck comparison flags
inked low-count payoffs, key 3–4-ofs never seen, and log cards that
aren't in the list.
Limits: the opponent's hand is hidden. Activated-ability costs and ink- drop payments aren't itemised in duels.ink logs, so ink math counts card costs paid. Tips are heuristics. Present them as things to check, not verdicts.
Args: log: The full duels.ink game log text. deck_list: Optional deck list the player used ("4x Card Name" per line). deck_path: Optional path to a file containing the deck list.
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": {
"log": "<log>"
},
"name": "analyze_game_log"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| log | Yes | ||
| deck_list | No | ||
| deck_path | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |