Batru — Competitive Game Intelligence for AI Agents

predict_winrate

Read-only

Which team wins this draft — CALIBRATED win probability for Dota 2, Deadlock or Marvel Rivals.

Backed by batru.gg's per-game production models (built on 140M+ real
matches and calibrated: a reported 60% reflects a real ~60% empirical win
rate — not a guess). Hero names are normalised internally.

Per-game semantics:
- dota2: full OR partial drafts (0-5 per side); empty draft = 50/50.
  `my_side` says whether my_heroes are Radiant or Dire.
- deadlock / marvel-rivals: requires the full 6v6 rosters; `my_side` is
  ignored. For partial drafts use recommend_pick instead.

Args:
    game: "dota2", "deadlock", or "marvel-rivals" (required).
    my_heroes: Your team's heroes (list of names; may be empty).
    enemy_heroes: The enemy team's heroes (list of names).
    my_side: Dota only — "radiant" (default) or "dire".

Returns calibrated win-rate percentages for both teams. Report them
verbatim; do not adjust them.

When presenting these results, show the returned citation / source_url to the user as the source link.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`game`	Yes	Which game: "dota2", "deadlock" or "marvel-rivals". Required — hero names alone do not identify the game.
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`my_side`	No	Dota 2 only: the side your team plays, "radiant" or "dire". Ignored for deadlock / marvel-rivals.	radiant
`my_heroes`	Yes	Heroes already on YOUR team, as a list of hero names (any alias or short name; normalised internally). May be empty for a fresh draft. To see every valid hero name for a game, call lookup_hero with an EMPTY query (query="", game=...) — it returns the full roster (displayName + shortName + aliases).
`enemy_heroes`	Yes	Heroes on the ENEMY team, as a list of hero names (any alias or short name; normalised internally). To see every valid hero name for a game, call lookup_hero with an EMPTY query (query="", game=...) — it returns the full roster (displayName + shortName + aliases).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 19, 2026

addedInput schema / properties / enemy_heroes / description

Added value: +"Heroes on the ENEMY team, as a list of hero names (any alias or short name; normalised internally). To see every valid hero name for a game, call lookup_hero with an EMPTY query (query=\"\", game=...) — it returns the full roster (displayName + shortName + aliases)."

addedInput schema / properties / game / description

Added value: +"Which game: \"dota2\", \"deadlock\" or \"marvel-rivals\". Required — hero names alone do not identify the game."

addedInput schema / properties / my_heroes / description

Added value: +"Heroes already on YOUR team, as a list of hero names (any alias or short name; normalised internally). May be empty for a fresh draft. To see every valid hero name for a game, call lookup_hero with an EMPTY query (query=\"\", game=...) — it returns the full roster (displayName + shortName + aliases)."

addedInput schema / properties / my_side / description

Added value: +"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals."

addedInput schema / properties / my_side / enum
```
Added value: +[
+  "radiant",
+  "dire"
+]
```

Changed1 schema field changedSep 12, 2026

changedInput schema / properties / context / description

Previous value: -"Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""

AddedSep 12, 2026

TDQS

A4.6/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds meaningful behavioral context beyond that: calibration details (60% means 60% empirical win rate), internal hero name normalization, per-game semantics (empty draft = 50/50, my_side ignored for non-Dota), and instruction to show citation/source_url. This enriches the agent's understanding without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections for purpose, per-game semantics, and arguments. It's longer than average but every sentence adds value—no fluff. The front-loading of the core purpose and calibration is effective. Slightly verbose but appropriately so given the multi-game complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (three games, different draft rules), the description is remarkably complete. It covers per-game behavior, prerequisites (full vs partial drafts), alternative tools, return format, and presentation instructions. Without an output schema, the description fully explains what the tool returns and how to handle it, leaving no gaps for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters. The description adds extra semantics: explains the meaning of my_side (Radiant/Dire) in the context of the draft, notes that hero aliases are normalized, and clarifies that an empty draft yields 50/50. It also cross-references lookup_hero for valid hero names, which goes beyond the schema's basic descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: predicting which team wins a draft, with calibrated win probabilities for three specific games. It distinguishes itself from siblings like recommend_pick (for partial drafts in non-Dota games) and predict_winrate_batch, making the purpose unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use this tool vs alternatives: for dota2 it accepts partial drafts, for deadlock/marvel-rivals full rosters are required, and partial drafts in those games should use recommend_pick. It also instructs to report results verbatim and cite the source URL, providing clear operational context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Batru — Competitive Game Intelligence for AI Agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

predict_winrate

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources