Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

get_matchup

Read-only

One hero vs one opponent — the measured head-to-head win rate in Dota 2, Deadlock, Marvel Rivals or League of Legends.

The direct matchup number ("does X beat Y?") from real games, with the
sample size. Names are normalised internally.

Args:
    game: "dota2", "deadlock", "marvel-rivals", or "lol".
    hero: Your hero.
    opponent: The enemy hero.

Report the number 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.
heroYesThe hero you are asking about (any alias; normalised internally).
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."
opponentYesThe opposing hero (any alias; normalised internally).

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: +"The hero you are asking about (any alias; normalised internally)."
    • addedInput schema / properties / opponent / description
      Added value: +"The opposing hero (any alias; normalised internally)."
  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.9/5.0
Behavior4/5

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

Annotations already cover readOnly=false destructive and openWorld, and the description adds genuinely new context: results come from real games, include a sample size, names are normalised internally, and the number must be reported verbatim with the citation/source_url surfaced. It does not mention error/empty-result behavior or rate limits, keeping it below a 5.

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?

Front-loaded with the core statement in the first line, followed by a clarification set and the output/citation instruction. The Args block is redundant with the 100%-covered schema and costs some space, but overall the text is tight and every remaining sentence carries an instruction.

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 carries the return-value burden and does so adequately: it says the result is a win rate with sample size plus a citation/source_url. It leaves open the failure mode for invalid or unrecognized hero names, which prevents a 5.

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 the game enum and the context field. The description's Args block largely restates these, adding only 'Names are normalised internally', which is already present in the schema descriptions for hero and opponent.

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+resource (measured head-to-head win rate for one hero vs one opponent) and adds the distinguishing scope 'direct matchup number' versus the sibling tools get_counters/predict_winrate. The four supported games are named up front, so an agent can tell immediately whether it applies.

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?

Usage is implied by 'the direct matchup number (does X beat Y?)', which signals a query-style call, but no sibling or alternative is named and there are no when-not-to-use conditions. An agent must infer on its own that get_counters or predict_winrate is the better choice for other questions.

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