liquipedia-dota2-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIQUIPEDIA_CACHE_PATH | No | Optional path to the SQLite cache file. Defaults to a system-appropriate location. | |
| LIQUIPEDIA_USER_AGENT | Yes | A custom User-Agent string containing a project name, version, and contact URL or email. Required to start the server. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_dota2_entitiesA | Search Liquipedia for Dota 2 tournaments, teams, or players. Use this before a detail tool when an exact canonical title is not already known. Multiple candidates require user confirmation. |
| get_dota2_tournamentA | Get tournament metadata, participants, and placements from an exact Liquipedia canonical title. Does not load matches; use list_dota2_matches when schedules or results are requested. |
| get_dota2_teamA | Get team metadata, roster, and coaches from an exact Liquipedia canonical title returned by search_dota2_entities. |
| get_dota2_playerA | Get player identity, current team, role, aliases, and team history from an exact Liquipedia canonical title returned by search_dota2_entities. |
| list_dota2_matchesA | List schedule or result rows for one exact tournament or team page. This is the expensive match-specific lookup; use only when the user asks about matches, schedules, scores, or results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct purpose: search for entities, then retrieve specific details for tournaments, teams, players, or matches. There is no overlap, and the descriptions clearly differentiate when to use each one.
All tools follow a consistent verb_noun pattern in snake_case (e.g., search_dota2_entities, get_dota2_tournament, list_dota2_matches). The naming is predictable and easy to understand.
With 5 tools, the server is well-scoped for a focused domain (Dota 2 esports data). It provides essential operations without unnecessary bloat or missing core functionality.
The toolset covers the full lifecycle of querying Dota 2 entities: search to find canonical titles, then retrieve details for tournaments, teams, players, and matches. There are no obvious gaps for a read-only information retrieval server.