Skip to main content
Glama

Batru — Dota 2, Deadlock & Marvel Rivals win predictor

by gg.batru

get_deadlock_tier_list_by_rank

Read-only

Get the Deadlock hero tier list for a specific rank band.

The meta differs by skill level. Data comes in four bands: Low
(Initiate-Acolyte), Mid (Sentinel-Ritualist), High (Emissary-Phantom) and
Top (Ascendant-Eternus). Early in a patch window a band may not have enough
matches yet — fall back to get_deadlock_tier_list if so.

Args:
    rank: A rank name (e.g. oracle, eternus) or a band key: low, mid,
        high, top.
    limit: Max number of heroes to return (default 20).

Returns {bracket, rank_range, total_matches, generated_at, heroes:[{hero,
rank, winrate_pct, pick_rate_pct, matches}]} sorted best-first. Report
numbers verbatim and mention which band the numbers come from.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rankYes
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

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is clear. The description adds value by stating the return structure explicitly (bracket, rank_range, total_matches, generated_at, heroes array with fields) and instructing the agent to report numbers verbatim and mention the band. The description also hints at potential data unavailability (early patch), which is a behavioral nuance beyond the annotations. It could be improved by noting any rate limits or how often data refreshes, but overall it's strong.

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 a brief purpose statement, followed by contextual details and usage guidelines, then explicit parameter descriptions, and finally return format and presentation instructions. The first sentence is a clear front-loaded purpose. Some of the output instructions (e.g., 'Report numbers verbatim') could be viewed as extra but are helpful for correct behavior. The final line about showing citation might be better in the return format section, but it's not excessive.

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 that there is no output schema, the description fully compensates by explicitly listing the return shape and fields. The 3 parameters are all explained with examples and defaults. The tool is moderately complex (rank band lookup), and the description covers the key nuance of data availability and fallback. No obvious gaps remain for an agent to invoke the tool correctly.

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

Parameters5/5

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

Schema description coverage is only 33% (2 of 3 params have docs). However, the description compensates by providing detailed semantics for 'rank' (e.g., examples 'oracle, eternus', band keys 'low, mid, high, top') and for 'limit' (default 20). The remaining parameter 'context' is documented in the schema with a thorough description of its purpose and usage rules. The description also adds the return structure which helps the agent understand how parameters affect the output.

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: 'Get the Deadlock hero tier list for a specific rank band.' It specifies the verb ('Get'), resource ('Deadlock hero tier list'), and the critical distinguishing dimension ('rank band'). It also explains why rank matters ('The meta differs by skill level'), which differentiates it from the sibling get_deadlock_tier_list (general list).

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?

The description provides explicit guidance on when to use this tool vs the fallback: 'Early in a patch window a band may not have enough matches yet — fall back to get_deadlock_tier_list if so.' This is a clear when-not condition with a named alternative. It also describes the four rank bands (Low, Mid, High, Top) and that rank can be a band key or a specific rank name, helping the agent select the correct input.

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