Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_tournament_game_stats

Read-only

Per-game BOX SCORES from parsed replays of a pro Dota 2 tournament.

For each game: lane winners at 10 minutes, every player's hero, lane,
K/D/A, GPM, net worth and key item timings, first blood, Roshans, and
comeback flags. Filter by team, stage, or a single match_id.

Args:
    event: Event slug (default "ti-2026").
    team: Optional team-name filter.
    stage: Optional stage filter.
    match_id: Optional single-match filter.
    limit: Max games to return (default 3).
    game: Only "dota2" today.

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

Input Schema

NameRequiredDescriptionDefault
gameNoOnly "dota2" has replay-parsed box scores today.dota2
teamNoOptional team-name filter (either side of the game).
eventNoEvent slug, e.g. "ti-2026" or "ewc-2026".ti-2026
limitNoMax games to return (each is a full box score).
stageNoOptional stage filter (group stage, playoffs, ...).
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."
match_idNoOptional: a single Dota match id to fetch; 0 = no filter.

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. Changed6 schema fields changed
    • addedInput schema / properties / event / description
      Added value: +"Event slug, e.g. \"ti-2026\" or \"ewc-2026\"."
    • addedInput schema / properties / game / description
      Added value: +"Only \"dota2\" has replay-parsed box scores today."
    • addedInput schema / properties / limit / description
      Added value: +"Max games to return (each is a full box score)."
    • addedInput schema / properties / match_id / description
      Added value: +"Optional: a single Dota match id to fetch; 0 = no filter."
    • addedInput schema / properties / stage / description
      Added value: +"Optional stage filter (group stage, playoffs, ...)."
    • addedInput schema / properties / team / description
      Added value: +"Optional team-name filter (either side of the game)."
  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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact stat payload per game (lane winners at 10 min, K/D/A, GPM, net worth, item timings, first blood, Roshans, comeback flags) and the note that each returned game is a full box score, which affects limit choices. It doesn't disclose pagination or data-coverage limits across events.

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 opening sentence front-loads purpose, and the field enumeration gives an agent a quick sense of payload. The Args block duplicates schema content and is somewhat redundant, but the citation instruction at the end earns its place for presentation behavior.

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?

With no output schema, the description compensates by enumerating the returned fields and flagging that each game is a full box score. Combined with annotations covering safety and open-world access, an agent has enough to call and present results correctly.

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 every parameter already has documented semantics and defaults. The description's Args block largely restates the schema (defaults for event/limit, the dota2-only caveat) with only marginal added nuance, so the 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?

States a specific verb and resource — per-game box scores from parsed replays of a pro Dota 2 tournament — and its emphasis on 'per-game' implicitly contrasts with the aggregate get_tournament_stats sibling. However, it never names that sibling explicitly, so the differentiation requires inference.

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 explains that you can filter by team, stage, or a single match_id, which implies when the tool is useful, but it gives no explicit 'use this instead of X when...' guidance relative to get_tournament_stats or get_matchup. Usage is implied rather than directed.

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