Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

opendota_live

Fetch current top live Dota 2 games with match and league IDs, team names, scores, game clock, net-worth lead, hero IDs, and source freshness for live match tracking.

Instructions

OpenDota live games. Returns OpenDota's current top live Dota 2 games: match and league IDs, team names, score, game clock, net-worth lead, player names when exposed, raw hero IDs, the upstream team code (0 or 1), and team slot (1, 2, 3, 4, or 5). The source mixes public matchmaking with tournament games; league_id is 0 when no league is associated, so its presence alone does not certify a professional event. delay_seconds and last_update_time report source freshness. Live player K/D/A is not provided by this endpoint. Resolve hero_id values with opendota_heroes.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses returned fields, source mixing, league_id=0 semantics, freshness fields, the absence of live player K/D/A, and the need to resolve hero IDs via opendota_heroes.

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 front-loaded with purpose and then gives dense, useful return-field and caveat details. Every sentence contributes either scope, returned data semantics, or a limitation, with 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?

For a no-parameter, read-only live-data endpoint with no output schema, the description is complete: it explains what is returned, what is not returned, how to interpret league and hero IDs, and how to judge freshness.

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?

The tool has zero parameters, so the baseline is 4 and there is no parameter syntax to explain. The description appropriately focuses on return fields and caveats instead of inventing parameter guidance.

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 names a specific verb and resource: it returns OpenDota's current top live Dota 2 games. It clearly distinguishes this from match-detail or history tools by emphasizing live games, and it routes hero ID resolution to the opendota_heroes sibling.

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 makes the use context clear: it is for current top live Dota 2 games. It also warns that the source mixes public matchmaking with tournament games and that league_id=0 does not certify a professional event, though it does not explicitly compare against alternatives like opendota_pro_matches or opendota_public_matches.

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

Deploy Server

Other Tools