Skip to main content
Glama
hkaanengin

opendota-mcp-server

by hkaanengin

get_hero_item_popularity

Retrieve item popularity statistics for any Dota 2 hero by game phase, showing the most bought items at start, early, mid, and late game to guide build decisions.

Instructions

Get item popularity statistics for a hero organized by game phase (start, early, mid, late).

Use this when users ask about:

  • "What items should I buy on Pudge?"

  • "Show me Anti-Mage's item build"

  • "What's the most popular starting items for Invoker?"

  • "What do people build late game on Phantom Assassin?"

  • "Show me Rubick's core items"

Returns aggregated item statistics from thousands of matches, useful for:

  • Understanding optimal item progression for a hero

  • Identifying core items vs situational items

  • Learning meta item builds and timings

  • Seeing which items are most popular at each game stage

Supports fuzzy matching for hero names:

  • "Pudge", "pudge", "PUDGE" all work

  • "Anti-Mage", "antimage", "anti mage" all work

  • "Shadow Fiend", "shadowfiend", "sf" all work

Args: hero: Hero name (display name, internal name, fuzzy match) or hero ID Examples: "Pudge", "antimage", "Shadow Fiend", 86

Returns: Dictionary with game phases as keys, each containing: - start_game_items: Items purchased at game start (0-10 min) - early_game_items: Items purchased early (0-25 min) - mid_game_items: Items purchased mid game (25-40 min) - late_game_items: Items purchased late game (40+ min)

Each phase contains item names mapped to their statistics:
- wins (int): Times this item was in winning matches
- games (int): Total matches where this item was purchased

Examples: get_hero_item_popularity("Anti-Mage") -> { "start_game_items": { "Quelling Blade": {"wins": 15234, "games": 25123}, "Tango": {"wins": 18234, "games": 26234}, "Slippers of Agility": {"wins": 12345, "games": 21234}, ... }, "early_game_items": { "Power Treads": {"wins": 8234, "games": 15234}, "Battle Fury": {"wins": 12234, "games": 18234}, ... }, "mid_game_items": { "Manta Style": {"wins": 9234, "games": 14234}, "Black King Bar": {"wins": 5234, "games": 8234}, ... }, "late_game_items": { "Butterfly": {"wins": 4234, "games": 6234}, "Abyssal Blade": {"wins": 3234, "games": 5234}, ... } }

get_hero_item_popularity(1)  # Anti-Mage by ID
-> Same format as above

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
heroYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details the return structure (game phases, wins/games), explains fuzzy matching for hero names, and notes that data comes from 'thousands of matches.' It does not explicitly state read-only nature or potential errors, but for a read-only 'get' tool this is fairly transparent.

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 well-structured with sections: purpose, use cases, return format, args, and examples. Every sentence adds value, and the content is directly relevant to invoking the tool correctly. Though long, the organization and front-loaded purpose make it easy to parse.

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?

For a single-parameter tool with rich output, the description is comprehensive. It fully documents the return structure, phase time ranges, and per-item statistics with examples. It also demonstrates the call format via example invocations. No important context is missing for an agent to use this tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only provides a type (integer or string) for the hero parameter with no enum, and schema coverage is 0%. The description compensates thoroughly by explaining 'Hero name (display name, internal name, fuzzy match) or hero ID' with concrete examples including alias handling. This fully disambiguates the parameter beyond what the schema offers.

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 a specific verb+resource+scope: 'Get item popularity statistics for a hero organized by game phase.' It clearly distinguishes from siblings like get_item_details (item info) or get_hero_matchups (hero matchups) by focusing on item popularity per hero. The example queries further reinforce the tool's purpose.

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?

The description provides explicit 'Use this when users ask about:' with multiple concrete example queries, making the intended usage clear. It also lists 'useful for' scenarios that help the agent decide when to invoke this tool. However, it does not mention when not to use or explicitly name alternative tools, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hkaanengin/opendota-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server