Skip to main content
Glama

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_tier_list

Read-only

Best heroes right now — the current-patch tier list for Dota 2, Deadlock or Marvel Rivals.

Empirical rankings from batru.gg's match aggregation over real games (not
a guess); heroes come sorted best-first. Optionally filter to a skill
bracket with `rank`.

Args:
    game: "dota2", "deadlock", or "marvel-rivals".
    rank: Optional skill bracket. dota2: herald, guardian, crusader,
        archon, legend, ancient (and bands). deadlock/marvel-rivals:
        low, mid, high, or top (rank words like "oracle" or "eternus"
        also resolve). Empty = all ranks combined.
    limit: Max heroes to return (default 20).

`total_matches` is the sample behind the ranking — cite it when stating
how strong the signal is. Report numbers verbatim.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameYesWhich game: "dota2", "deadlock" or "marvel-rivals". Required — hero names alone do not identify the game.
rankNoOptional skill bracket. dota2: herald, guardian, crusader, archon, legend, ancient (or a band like "legend-ancient"). deadlock / marvel-rivals: low, mid, high or top. Empty = all ranks.
limitNoMaximum number of rows to return.
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / game / description
      Added value: +"Which game: \"dota2\", \"deadlock\" or \"marvel-rivals\". Required — hero names alone do not identify the game."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of rows to return."
    • addedInput schema / properties / rank / description
      Added value: +"Optional skill bracket. dota2: herald, guardian, crusader, archon, legend, ancient (or a band like \"legend-ancient\"). deadlock / marvel-rivals: low, mid, high or top. Empty = all ranks."
  2. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Explain 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.\""New value: +"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses that rankings come from real match aggregation 'not a guess,' that heroes are sorted best-first, that total_matches is the sample behind the ranking, and that results include citation/source_url to show the user. It also instructs reporting numbers verbatim. This is substantial added behavioral context.

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 front-loaded with the core purpose and keeps parameter documentation compact. It has slight redundancy with the schema's param descriptions, but the added notes on rank resolution and citation behavior earn their place. It is appropriately sized for a tool with four parameters.

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 compensates by describing return behavior: heroes sorted best-first, limit for max rows, total_matches as the sample size, and citation/source_url to display. It does not specify the exact response shape per hero, but it provides enough for an agent to invoke the tool and use the results correctly.

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?

Schema coverage is 100%, so the schema already documents game, rank, limit, and context. The description adds extra meaning by explaining rank bands, stating that rank words like 'oracle' or 'eternus' also resolve, and clarifying that empty rank means all ranks combined. This goes beyond the schema's enum values.

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 phrase 'Best heroes right now — the current-patch tier list' states a specific verb, resource, and scope across three named games. It also communicates that results are 'Empirical rankings from batru.gg's match aggregation' and 'sorted best-first,' which cleanly distinguishes it from sibling tools like get_ban_rates or get_counters.

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 makes the use case clear: retrieve the current-patch tier list when the user wants the best heroes, optionally filtered by skill bracket. It does not explicitly name alternatives or exclusions, but the context is strong enough that an agent can infer when this tool is appropriate.

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

All Batru — Competitive Game Intelligence for AI Agents toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources