Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

predict_winrate

Read-only

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

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.
- lol: requires the full 5v5 rosters (Blue = my_heroes, Red = enemy_heroes)
  in role order TOP, JUNGLE, MID, BOT, SUPPORT; `my_side` is ignored.

Args:
    game: "dota2", "deadlock", "marvel-rivals", or "lol" (required).
    my_heroes: Your team's heroes (list of names; may be empty for Dota).
    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

NameRequiredDescriptionDefault
gameYesWhich game: "dota2", "deadlock", "marvel-rivals" or "lol" (League of Legends). Required — hero names alone do not identify the game.
contextYesExplain 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_sideNoDota 2 only: the side your team plays, "radiant" or "dire". Ignored for deadlock / marvel-rivals / lol.radiant
my_heroesYesHeroes 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_heroesYesHeroes 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.

  1. Changed3 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Which game: \"dota2\", \"deadlock\" or \"marvel-rivals\". Required — hero names alone do not identify the game."New value: +"Which game: \"dota2\", \"deadlock\", \"marvel-rivals\" or \"lol\" (League of Legends). Required — hero names alone do not identify the game."
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "dota2",
-  "deadlock",
-  "marvel-rivals"
-]New value: +[
+  "dota2",
+  "deadlock",
+  "marvel-rivals",
+  "lol"
+]
    • changedInput schema / properties / my_side / description
      Previous value: -"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals."New value: +"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals / lol."
  2. Changed5 schema fields changed
    • 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"
+]
  3. Changed1 schema field changed
    • 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.\""
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses model provenance, calibration behavior, hero-name normalization, empty-draft behavior, and the need to report returned probabilities verbatim. It also tells the agent to surface citation/source_url, which is meaningful behavioral context for presenting results.

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 front-loaded with purpose and then organized by game, which suits the complexity. The Args section partly duplicates the input schema and omits context, so it is not maximally tight, but it remains readable and purposeful.

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?

For a complex four-game prediction tool with no output schema, the description is complete enough: it covers input requirements, game-specific semantics, return values, and citation behavior. An agent has the information needed to call it correctly and present results appropriately.

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 already 100%, but the description adds useful cross-parameter semantics: Dota allows partial drafts, Deadlock and Marvel Rivals require full 6v6, and LoL requires full 5v5 rosters in role order. It does not explain the required context parameter, but the schema fully documents that parameter.

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 that this tool predicts calibrated draft win probability and names the supported games. It also distinguishes its scope from siblings by directing partial-draft Deadlock/Marvel Rivals users to recommend_pick instead.

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

Usage Guidelines4/5

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

It gives explicit per-game usage rules, including when full rosters are required and when my_side is ignored, and it names recommend_pick as the alternative for partial drafts in two games. It does not address other close siblings such as predict_winrate_batch or analyze_draft, so the routing guidance is strong but not exhaustive.

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 toolsInspect
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.

Resources