Skip to main content
Glama

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

TableJSON 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. 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)."
  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.2/5.0
Behavior4/5

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

Annotations already mark it read-only, open-world, and non-destructive; the description adds useful caveats: data comes from parsed replays, only dota2 has box scores today, and the citation/source_url must be surfaced to the user. No contradiction with 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 the core purpose, followed by a concise field list, parameter bullets, and a display instruction. The Args bullet list duplicates schema text somewhat, but the structure keeps it scannable and no part is misleading.

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?

Even with no output schema, the description names the returned data fields and the citation/source_url display requirement, and the schema fully documents all parameters including the required context argument. An agent has everything needed to invoke the tool 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 the baseline is 3. The Args list mostly restates the schema's defaults and descriptions; the only extra semantic is grouping team/stage/match_id as filters, which is marginal.

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 opens with 'Per-game BOX SCORES from parsed replays of a pro Dota 2 tournament' and then enumerates exactly what each box score contains, such as lane winners, K/D/A, GPM, item timings, and Roshans. This clearly identifies a read-only retrieval of per-game stats and differentiates it from sibling tools like get_tournament_stats or get_ban_rates by scope and source.

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 gives clear context: use when per-game Dota 2 box scores are needed, with optional filters by team, stage, or match_id, and it notes that only 'dota2' is supported today. It does not explicitly name alternatives or say when not to use this tool, so it stops short of a 5.

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