Skip to main content
Glama

Batru — Dota 2, Deadlock & Marvel Rivals win predictor

by gg.batru

get_dota_tier_list

Read-only

Best Dota 2 heroes right now — the current-patch meta tier list from real games.

Ranked by batru.gg's match aggregation over ~real games — empirical meta, not
a guess. Heroes come sorted best-first (rank 1 = strongest). Report numbers
verbatim.

Args:
    limit: Max number of heroes to return (default 20).

Returns {total_matches, generated_at, heroes:[{hero, rank, winrate_pct,
pick_rate_pct, matches}]}. `total_matches` is the sample the ranking is drawn
from — cite it when stating how strong the signal is.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
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."

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds useful behavioral detail beyond that: data source (batru.gg), empirical aggregation, sort order, and the instruction to report numbers verbatim and cite total_matches. It also explains what the returned object contains, which helps the agent interpret the result.

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 Args and Returns sections and front-loaded with the headline purpose. It is slightly verbose and contains a minor typo ('~real games') plus an inconsistency where `citation`/`source_url` are referenced but not listed in the described return object.

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?

For a read-only list tool with no output schema, the description provides enough operational detail: return shape, meaning of total_matches, sorting semantics, and the instruction to surface the source link. The unresolved mention of `citation`/`source_url` not present in the stated return object is a small completeness gap.

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 schema only fully describes the `context` parameter, while `limit` has no description. The description compensates by explicitly documenting `limit` as 'Max number of heroes to return (default 20).' This fills the main schema gap, though it does not add anything beyond that.

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

Purpose4/5

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

The description clearly states what the tool does: returns the current-patch Dota 2 meta tier list based on real-game aggregation, sorted best-first. It does not explicitly contrast itself with the sibling get_dota_tier_list_by_rank, but the 'rank 1 = strongest' framing makes the base-list purpose clear enough.

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

Usage Guidelines3/5

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

Usage context is implied through 'Best Dota 2 heroes right now' and 'empirical meta, not a guess,' but there is no explicit guidance about when to prefer this tool over alternatives like get_dota_tier_list_by_rank, get_dota_counters, or matchup tools. No exclusions or conditional routing are provided.

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