Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_hero_momentum

Read-only

Which heroes are rising or falling right now — week-over-week win-rate movement.

Momentum from batru.gg's rolling match aggregation for Dota 2, Deadlock
or Marvel Rivals: the biggest movers of the current window, or one hero's
trend when `hero` is given.

Args:
    game: "dota2", "deadlock", or "marvel-rivals".
    hero: Optional — one hero's momentum instead of the movers list.
    limit: Max movers to return (default 10).

Report numbers verbatim.

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

Input Schema

NameRequiredDescriptionDefault
gameYesWhich game: "dota2", "deadlock", "marvel-rivals" or "lol" (League of Legends). Required — hero names alone do not identify the game.
heroNoOptional: one hero to report on. Empty = the biggest movers of the current window.
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. Changed2 schema fields changed
    • changedInput schema / properties / game / description
      Previous value: -"Which game: \"dota2\", \"deadlock\" or \"marvel-rivals\". Required — hero names alone do not identify the game."New value: +"Which game: \"dota2\", \"deadlock\", \"marvel-rivals\" or \"lol\" (League of Legends). Required — hero names alone do not identify the game."
    • changedInput schema / properties / game / enum
      Previous value: -[
-  "dota2",
-  "deadlock",
-  "marvel-rivals"
-]New value: +[
+  "dota2",
+  "deadlock",
+  "marvel-rivals",
+  "lol"
+]
  2. 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 / hero / description
      Added value: +"Optional: one hero to report on. Empty = the biggest movers of the current window."
    • 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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so safety is covered. The description adds genuinely non-structured context: the upstream citation obligation ('report numbers verbatim', show `citation`/`source_url`), which materially affects how an agent presents results.

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 purpose and data source are front-loaded in two sentences, and the output-hygiene note comes last. The Args block largely duplicates the schema descriptions, which is mild waste but keeps the call usable without schema lookup.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description only hints at the return shape via `citation`/`source_url`. It does not say what a momentum record contains (win-rate delta, sample size, window length), and the game-list mismatch with the schema leaves a real ambiguity for a read tool an agent may call speculatively.

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 enum, defaults, and empty-string semantics for `hero` are already documented — description adds little beyond restating them. It also introduces an inconsistency: the prose lists only dota2/deadlock/marvel-rivals while the schema enum includes "lol", leaving the agent unsure whether LoL is actually supported.

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?

States a specific verb and resource — 'week-over-week win-rate movement' for heroes — plus the exact data source (batru.gg rolling match aggregation) and the two modes (movers list vs. single-hero trend). An agent can distinguish this from get_tier_list, get_ban_rates, or lookup_hero without opening a schema.

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?

Clear about the two call modes: omit `hero` for the biggest movers, supply `hero` for a single trend. It never names a sibling alternative (e.g. get_tier_list when the user wants absolute win rates rather than movement), so it stops short of a full routing guide.

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