get_dota_tournament_game_stats
shallowgg.batru/batru-mcp · Verify this server
Get per-game BOX SCORES from parsed replays for a pro Dota 2 tournament. For each game: which team won each lane at 10 minutes (gold diff), every player's hero, lane, K/D/A, GPM, net worth and key item timings (BKB, Blink, ...), first blood time, Roshan kills, and whether the winner came back from a large gold deficit. Answers questions like "who won mid in game 2 of Spirit vs VISION", "when did Yatoro's BKB come online", "did they throw a lead". REAL parsed-replay facts (via OpenDota), not model output. A just-finished game can lag ~an hour until its replay is parsed. Covered: The International 2026 ("ti-2026"; other events don't carry per-game data yet). Filter by bracket stage ("grand final", "lower bracket final", "semifinal", "quarterfinals", "elimination"...) when the user asks about a round rather than a team; by team name (substring, e.g. "spirit"); or by match_id for one exact game. No filter = the event's most recent games. Don't know the teams or stages? Call get_dota_tournament_stats first — its playoff_results list the whole bracket with stage labels. Args: event: Tournament slug or alias (default "ti-2026"). team: Optional team-name filter, case-insensitive substring. stage: Optional bracket-stage filter, case-insensitive substring of the stage label (e.g. "grand final", "upper bracket final", "lower bracket semifinal", "semifinal"). match_id: Optional exact match id for a single game. limit: Max games returned, newest first (default 3, cap 5). Returns {event, as_of, games:[{series:{phase, day, team1, score, team2}, match_id, winner, radiant, dire, duration_s, kills, first_blood_s, roshan_kills?, winner_max_gold_deficit?, lanes?, players:[{team, hero, player, lane, kda, gpm, net_worth, key_items?}]}], citation}. Include the citation when presenting results. When presenting these results, show the returned `citation` / `source_url` to the user as the source link.
1 trials · measured 50 days ago
get_dota_tournament_game_stats scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against gg.batru/batru-mcp, measured 31 Aug 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote + stdio
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-08-31 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/c6477216-c9a9-4b65-8d2e-0eac71f25986)