Skip to main content
Glama
Sign In

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

recommend_pick

Read-only

Best heroes to pick next against this draft — Dota 2, Deadlock, Marvel Rivals or League of Legends.

Per-game semantics:
- dota2: top 3 picks scored by the CALIBRATED draft model (each with the
  calibrated team win rate after adding that hero); `my_side` applies.
- deadlock / marvel-rivals / lol: ranked by REAL observed pair data (win
  rate vs the enemy heroes, blended with duo rate alongside your picks) — an
  empirical heuristic, not the calibrated model; verify a full roster with
  predict_winrate.

Args:
    game: "dota2", "deadlock", "marvel-rivals", or "lol".
    enemy_heroes: Enemy heroes to pick against.
    my_heroes: Heroes your team already has.
    my_side: Dota only — "radiant" (default) or "dire".
    limit: Max recommendations (Deadlock/Marvel/LoL; Dota returns top 3).

Report win rates 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.
limitNoMax recommendations (Deadlock / Marvel Rivals / LoL; Dota always returns its top 3).
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."
my_sideNoDota 2 only: the side your team plays, "radiant" or "dire". Ignored for deadlock / marvel-rivals / lol.radiant
my_heroesNoHeroes your team already has, as a list of hero names (may be empty).
enemy_heroesYesEnemy heroes to pick against, as a list of hero names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
+]
    • changedInput schema / properties / limit / description
      Previous value: -"Max recommendations (Deadlock / Marvel Rivals; Dota always returns its top 3)."New value: +"Max recommendations (Deadlock / Marvel Rivals / LoL; Dota always returns its top 3)."
    • changedInput schema / properties / my_side / description
      Previous value: -"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals."New value: +"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals / lol."
  2. Changed6 schema fields changed
    • addedInput schema / properties / enemy_heroes / description
      Added value: +"Enemy heroes to pick against, as a list of hero names."
    • 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 / limit / description
      Added value: +"Max recommendations (Deadlock / Marvel Rivals; Dota always returns its top 3)."
    • addedInput schema / properties / my_heroes / description
      Added value: +"Heroes your team already has, as a list of hero names (may be empty)."
    • addedInput schema / properties / my_side / description
      Added value: +"Dota 2 only: the side your team plays, \"radiant\" or \"dire\". Ignored for deadlock / marvel-rivals."
    • addedInput schema / properties / my_side / enum
      Added value: +[
+  "radiant",
+  "dire"
+]
  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.6/5.0
Behavior5/5

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

Annotations already cover read-only, open-world, and non-destructive behavior. The description adds substantial context beyond annotations: model differences by game, empirical-vs-calibrated caveat, Dota-only my_side, Dota's fixed top 3, limit behavior elsewhere, and instructions to report win rates verbatim and show the citation/source_url.

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 purpose and structured with per-game semantics plus Args. It is appropriately sized for a complex multi-game tool, though the Args list repeats schema-covered details and slightly reduces concision.

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?

Given six parameters, no output schema, and cross-game behavior, the description provides enough detail about return values, model limitations, and required user-facing citation behavior for an agent 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.

Parameters4/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, but the description adds meaningful semantics: game-specific scoring, my_side applies only to Dota, limit applies only to non-Dota games, and Dota always returns top 3. Some parameter details duplicate the schema, but the added per-game meaning is useful.

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 action and resource: recommending best heroes to pick next against a draft, across four named games. It also distinguishes per-game scoring behavior and returns, so an agent can tell what the tool does without opening the 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?

Explains that Dota 2 uses the calibrated draft model while Deadlock, Marvel Rivals, and LoL use empirical pair data, and says to verify full rosters with predict_winrate. It does not explicitly compare against analyze_draft or other sibling draft tools, so the when-to-use guidance is clear but not exhaustive.

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