Skip to main content
Glama

Batru — Competitive Game Intelligence for AI Agents

by gg.batru
OverviewDiscussionsAdmin

lookup_hero

Read-only

Normalise a hero name/alias/shortName to its canonical identity — or list the whole roster.

Use this to turn messy user input ("am", "anti mage", "Anti-Mage") into the
exact key batru.gg expects before calling the prediction tools. The backend
SILENTLY DROPS hero names it doesn't recognise, so always normalise first.
Not sure which heroes exist? Call it with an EMPTY query to get every hero
of that game (displayName, shortName, aliases).

Args:
    query: A hero name, alias, or short name. Empty string = list the full roster.
    game: "dota2" (default), "deadlock", or "marvel-rivals".

Returns {id, displayName, shortName, game} for the best match, an error
with `did_you_mean` candidates if nothing matches, or — for an empty
query — {game, count, heroes:[{id, displayName, shortName, aliases}]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gameNo"dota2" (default), "deadlock", or "marvel-rivals".dota2
queryYesA hero name, alias or short name as the user typed it. Pass an EMPTY string to list the game's full roster instead.
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
    • addedInput schema / properties / game / description
      Added value: +"\"dota2\" (default), \"deadlock\", or \"marvel-rivals\"."
    • addedInput schema / properties / query / description
      Added value: +"A hero name, alias or short name as the user typed it. Pass an EMPTY string to list the game's full roster instead."
  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. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "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.\"",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "context"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses a critical backend behavior: unrecognised hero names are silently dropped. It also explains the error shape (did_you_mean candidates) and the empty-query roster response. This is valuable behavioral context an agent would not otherwise know.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded with the core purpose. Subsequent sentences each add necessary operational detail: silent-drop warning, empty-query roster behavior, args, and return shapes. No filler.

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?

There is no output schema, so the description appropriately covers return values for all three cases: match, error, and roster list. Combined with the rich schema and safe annotations, an agent has everything needed to call this 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?

The schema already documents query and game with 100% coverage. The description slightly reinforces query semantics (empty string = roster) but largely repeats the schema and does not add deeper parameter-level insight. It also omits the required context parameter, although the schema describes it well.

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 first sentence states a specific verb (normalise), a specific resource (hero name/alias/shortName), and the fallback mode (list roster). It also tells the agent why this matters: the exact key batru.gg expects before prediction tools. This makes it clearly distinct from sibling prediction/stats tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use it: to convert messy user input before calling prediction tools. It also gives a conditional usage rule: if unsure which heroes exist, call with an empty query. This is actionable and contextual.

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