Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_ban_rates

Read-only

Most-banned heroes — measured draft-phase ban rates for Deadlock or Marvel Rivals.

Args:
    game: "deadlock" or "marvel-rivals" (ranked Dota has no ban-phase
        export — for pro Dota bans use get_tournament_stats).
    limit: Max heroes to return (default 15).

Report numbers verbatim.

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

Input Schema

NameRequiredDescriptionDefault
gameYes"deadlock" or "marvel-rivals" (Dota 2 has no draft-phase ban data here).
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. Changed1 schema field changed
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "dota2",
-  "deadlock",
-  "marvel-rivals"
-]New value: +[
+  "dota2",
+  "deadlock",
+  "marvel-rivals",
+  "lol"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / game / description
      Added value: +"\"deadlock\" or \"marvel-rivals\" (Dota 2 has no draft-phase ban data here)."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of rows to return."
  3. 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.\""
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this a safe read-only, open-world call, so the bar is lower. The description still adds real behavioral guidance: report numbers verbatim, and surface the returned citation/source_url as the source link — output-handling rules the annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The 'most-banned heroes' purpose is front-loaded in the first clause, alternatives and output rules follow in short order, and no sentence is filler. The Args listing is mildly redundant with the schema but brief.

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 data tool with no output schema, the definition covers scope, the Dota fallback, and citation handling. The remaining gap is the mismatch between the four-value enum and the two games the description claims, which could cause a failed 'lol' call.

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

Parameters3/5

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

Schema coverage is 100%, so game and limit are already documented with an enum and a default of 15; the description's Args block largely restates them. It adds no new semantics and, worse, under-describes the enum by naming only two of the four accepted games.

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 names a specific resource and scope — 'most-banned heroes, measured draft-phase ban rates' — and explicitly restricts it to Deadlock/Marvel Rivals, which is enough to distinguish it from tier-list and matchup siblings.

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?

It explicitly excludes ranked Dota and redirects to get_tournament_stats for pro Dota bans, which is exactly the kind of routing an agent needs. It stops short of saying when to prefer this over get_tier_list or get_hero_momentum, and never mentions the 'lol' value that the schema enum permits.

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