Skip to main content
Glama

Batru — Dota 2, Deadlock & Marvel Rivals win predictor

by gg.batru

recommend_dota_pick

Read-only

Recommend the top 3 Dota 2 heroes to pick next, with calibrated win rates.

Backed by batru.gg's production model. Each suggestion comes with the
CALIBRATED win rate your team would have after adding that hero against the
given enemy draft (a reported 60% reflects a real ~60% empirical win rate).
Hero names are normalised internally.

Args:
    my_heroes: Heroes your team has already picked (names/aliases, 0-4).
    enemy_heroes: Enemy heroes (names/aliases, 0-5).
    my_side: "radiant" (default) or "dire" — which side is "my_heroes".

Returns a list of up to 3 {displayName, shortName, win_rate_pct}. Report the
win rates verbatim.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextYesExplain 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."
my_sideNoradiant
my_heroesYes
enemy_heroesYes

TDQS

A4.4/5.0
Behavior4/5

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

The description explains calibration meaning, internal hero name normalization, return list length, and the instruction to show citation/source_url. These details go beyond the annotations (readOnlyHint, openWorldHint, destructiveHint) and add valuable behavioral context. No contradiction with annotations.

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

Conciseness5/5

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

Each paragraph has a distinct purpose: purpose, calibration/normalization, Args, and output/usage. The description is front-loaded with the main functionality and contains no redundant sentences.

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

Completeness4/5

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

With no output schema, the description fills in the return shape and provides usage instructions. It misses the required context parameter and edge cases like empty hero lists, but covers the core functionality thoroughly enough for an agent to correctly invoke the tool.

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?

The description explains my_heroes (0-4), enemy_heroes (0-5), and my_side default/meaning, which the schema leaves as bare titles. However, it omits the required context parameter entirely, which has a detailed schema description but is absent from the Args section, possibly causing an agent to overlook its 15-25 word instruction.

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 opening sentence clearly states the tool recommends the top 3 Dota 2 heroes to pick next with calibrated win rates. This distinguishes it from sibling tools like get_dota_counters or predict_dota_winrate by focusing on actionable draft recommendations.

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?

The description provides clear context for when to use the tool: given your already-picked heroes and enemy draft, it recommends the next best picks. It does not explicitly mention exclusions or alternatives, but the use case is strongly implied and the Args section clarifies input constraints.

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

All Batru — Dota 2, Deadlock & Marvel Rivals win predictor toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools are clearly separated by game prefix and metric family (tier list, counters, matchup, synergy, momentum, ban rates), so an agent can generally pick the right one. A few close pairs—counters vs. matchup and recommend vs. predict/batch—have adjacent purposes, and get_more_tools is a vague catch-all, so it is not quite a perfect 5.

Naming Consistency4/5

With a few exceptions the set follows a consistent get_<game>_<metric> / predict_* / recommend_* snake_case pattern. Deviations such as predict_dota_winrate instead of predict_dota_draft, predict_dota_winrate_batch, lookup_hero, and get_more_tools break the otherwise tidy pattern.

Tool Count2/5

32 tools is above the 25+ threshold and makes the server heavy even though the tri-game structure is logical. Many parallel families could be parameterized by game, and get_more_tools adds count without a clear domain purpose.

Completeness4/5

The read-only analytics surface is broadly complete: every game has tier lists, counters, matchups, synergies, momentum, draft prediction, and pick recommendations, plus Dota tournament coverage and a model track record. Gaps are minor—Dota lacks ladder ban rates, Deadlock and Marvel Rivals lack tournament stats and model evaluation ledgers, and their draft advice is only heuristic until six heroes are provided.

Resources