Skip to main content
Glama

Batru — Dota 2, Deadlock & Marvel Rivals win predictor

by gg.batru

get_deadlock_tier_list

Read-only

Best Deadlock heroes right now — the current meta tier list from real games.

Ranked by batru.gg's match aggregation — 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}]}. Cite `total_matches` for the sample size.

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

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's burden is lower. It adds useful context about real-game data, sorted ordering, and presentation rules like 'Report numbers verbatim' and 'Cite total_matches for the sample size.' However, it lists a return shape that omits citation/source_url, then instructs to 'show the returned citation / source_url,' creating an internal inconsistency about the actual return payload.

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-organized with front-loaded purpose, then Args, Returns, and presentation sections. Each sentence serves a purpose, and there is minimal fluff. The main flaw is the inconsistent mention of citation/source_url not in the stated Returns shape, which is a clarity issue rather than a conciseness issue.

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

Completeness2/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 correctly supplies a return shape, which is necessary. But it fails to mention the required context parameter and its special constraints, and the ambiguous citation/source_url guidance leaves the exact response structure unclear. These are material gaps for correct invocation and result presentation.

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

Parameters2/5

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

The description documents limit ('Max number of heroes to return (default 20)'), which adds a bit beyond the schema's bare integer type. But it completely omits the required context parameter, which carries strict 15-25 word third-person instructions. An agent reading only the tool description could easily invoke the tool without the mandatory context and fail schema validation.

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 identifies the tool's purpose: 'Best Deadlock heroes right now — the current meta tier list from real games.' It adds concrete detail about ordering ('sorted best-first (rank 1 = strongest)') and provenance ('empirical meta, not a guess'). However, it does not explicitly distinguish this tool from the sibling tool get_deadlock_tier_list_by_rank, which an agent might confuse with the overall meta tier list.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives like get_deadlock_tier_list_by_rank, get_deadlock_counters, or get_deadlock_matchup. It states what the tool returns but offers no 'use this when' or 'prefer this tool over X' instructions. An agent must infer the appropriate selection from the tool name and sibling names alone.

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