Skip to main content
Glama

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_tournament_stats

Read-only

TI / EWC pro tournament stats — actual most-picked, most-banned and win rates per hero.

Real recorded results from the official drafts of every game at a covered
pro Dota 2 event (The International, Esports World Cup, ...) — small-sample
records, not calibrated probabilities. Answers "most picked / banned /
contested at TI", "who won", "group standings".

Args:
    event: Event slug, e.g. "ti-2026" (default), "ti-2025",
        "esports-world-cup-2026".
    limit: Max heroes per table (default 15).
    game: Only "dota2" today.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameNoOnly "dota2" has pro tournament coverage today.dota2
eventNoEvent slug, e.g. "ti-2026" (The International 2026) or "ewc-2026" (Esports World Cup).ti-2026
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 / event / description
      Added value: +"Event slug, e.g. \"ti-2026\" (The International 2026) or \"ewc-2026\" (Esports World Cup)."
    • addedInput schema / properties / game / description
      Added value: +"Only \"dota2\" has pro tournament coverage today."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of rows to return."
  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

A3.9/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description warns that these are small-sample recorded results, not calibrated probabilities, and instructs the agent to display the returned citation/source_url. This provides meaningful behavioral context about data reliability and output handling without contradicting 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 front-loaded with a summary, followed by data caveats, example questions, Args, and a citation instruction. It is well organized and mostly efficient, though the Args section partially duplicates the schema.

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 does enough by naming the returned metrics and the source-link requirement. It omits the required 'context' parameter from its Args summary, but the schema carries an extensive explanation for that parameter, so the tool remains callable.

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 description coverage is 100%, so the schema already documents all four parameters, including defaults and the event slug format. The description adds little beyond restating the defaults and the 'only dota2' restriction, so a baseline 3 is appropriate.

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 resource (TI/EWC pro tournament stats) and the specific outputs (most-picked, most-banned, win rates per hero, standings). It is easy to understand what the tool returns, though it does not explicitly contrast itself with siblings like get_tournament_game_stats or get_ban_rates.

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 by focusing on aggregate tournament statistics and by listing example questions ('most picked / banned / contested at TI'). However, it never explicitly tells the agent when to prefer this tool over alternatives or when not to use it, leaving the sibling distinction to inference.

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