Skip to main content
Glama

Batru — Dota 2, Deadlock & Marvel Rivals win predictor

by gg.batru

get_marvel_rivals_tier_list

Read-only

Best Marvel Rivals heroes right now — the current-season 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

A3.7/5.0
Behavior4/5

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

The annotations already mark the tool as read-only and non-destructive, and the description adds meaningful behavioral context: the data source, empirical aggregation, best-first sorting, and the instruction to cite the sample size. The only minor inconsistency is that the return shape listed does not include citation/source_url even though the description tells the agent to show those fields, but this does not contradict the annotations.

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 and front-loaded with the core purpose, then moves through ranking source, sort order, parameters, return shape, and presentation instructions. It is slightly redundant in places, such as emphasizing empirical/meta after already saying 'from real games,' but overall every section earns its place and the formatting is scannable.

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

Completeness3/5

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

For a tool with no output schema, the description provides a reasonable return shape, sort order, and citation guidance. However, it does not explicitly differentiate from the by-rank sibling tool, and it instructs showing citation/source_url while omitting those fields from the listed return structure, which leaves a small but meaningful 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 description adds real semantic value for limit by stating it is the maximum number of heroes to return, which the schema does not explain beyond its default value. It omits the required context parameter from the Args section, but the schema itself provides a detailed and explicit description of context, so the missing natural-language coverage does not harm agent understanding.

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 the tool's purpose: it returns the current-season Marvel Rivals meta tier list, with heroes sorted best-first. It is specific about the resource (Marvel Rivals heroes) and the ranking basis (batru.gg match aggregation). However, it does not explicitly distinguish itself from the sibling get_marvel_rivals_tier_list_by_rank, so the differentiation is implied rather than stated.

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?

The description implies when to use it: when the user wants current-season Marvel Rivals hero meta or tier rankings. It gives clear presentation guidance, such as reporting numbers verbatim, citing total_matches, and showing citation/source_url, but it does not explicitly state when not to use it or direct the agent to any alternative sibling tools.

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