liquipedia-dota2

Liquipedia Dota 2

Use the read-only MCP tools to answer Dota 2 esports questions with revision-level provenance. Treat missing or unparsed data as unknown.

Workflow

1. Identify whether the request concerns a tournament, team, player, roster, schedule, score, or result.
2. Call search_dota2_entities unless the conversation already contains an exact canonical_title returned by that tool.
3. When search returns multiple plausible candidates, present the candidates and ask the user to choose. Stop before calling a detail tool. Never select solely from search rank.
4. Call exactly one matching detail tool:
   • Use get_dota2_tournament for tournament metadata, participants, and placements.
   • Use get_dota2_team for team metadata, roster, and coaches.
   • Use get_dota2_player for player identity, current team, role, aliases, and team history.
5. Call list_dota2_matches only when the user asks for matches, schedules, scores, or results. Pass the confirmed tournament or team canonical_title.
6. Inspect ok, coverage, warnings, and source before composing the answer. Read references/schema.md when exact result semantics or error recovery is needed.

Answering rules

• Answer in the user's language while preserving official names and handles.
• Use only returned fields for Liquipedia-backed claims. Do not fill null, partial, or unavailable fields from memory.
• Distinguish an empty result from unavailable parsing. Explain relevant warnings briefly.
• Convert UTC dates to the user's requested timezone only when the timezone is known; retain UTC otherwise.
• End with the Liquipedia page link and the source.fetched_at time. Mention stale cache when source.is_stale is true.
• Attribute the data to Liquipedia. Do not imply that Liquipedia or Team Liquid endorses the answer.

Failure handling

• If an MCP tool is unavailable, tell the user that the local liquipedia-dota2-mcp server must be configured; do not substitute HTML scraping.
• For ambiguous, show error.candidates and request confirmation.
• For rate_limited, report retry_after_seconds and avoid immediate retry loops.
• For not_found, offer a narrower spelling or entity-type search.
• For parse_failed or coverage: unavailable, state that the page structure is unsupported and link the source when provided.
• For upstream_unavailable, use stale data only when the tool explicitly returned it as a successful envelope.