Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

opendota_live

Read-only

Returns the current top live Dota 2 games: match and league IDs, teams, score, game clock, net-worth lead, delay, spectators and player hero/team slots. team_code values are 0 or 1 and team_slot values are 1 to 5. The source can include ordinary public matchmaking alongside tournaments; league_id zero means no league is associated, and a nonzero league ID alone does not prove an event is professional. delay_seconds and last_update_time carry freshness, and live K/D/A is not available here. Use opendota_heroes to resolve hero IDs. An empty matches list is valid when no games are live.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "opendota_live"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses important behavioral context: the data source may include public matchmaking, league_id interpretation is ambiguous, delay_seconds and last_update_time indicate freshness, and live K/D/A is unavailable. These details materially reduce the risk of over-interpreting the response.

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 first sentence front-loads the tool purpose, and subsequent sentences each add concrete caveats or field guidance. Despite the density, there is no filler or repetition.

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 zero-parameter live-data tool with annotations covering safety and an output schema, the description supplies all necessary operational context: scope, freshness signals, known data limitations, and valid empty-result behavior. Nothing essential is missing for correct invocation.

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 takes no parameters, so there is no parameter syntax to explain and a baseline of 4 is appropriate. The description still clarifies returned-field semantics such as team_code and team_slot ranges, though those are output rather than input semantics.

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 states a specific verb and resource: it returns current top live Dota 2 games, then enumerates the returned game and player fields. It also distinguishes its scope from pro-only data by warning that public matchmaking can appear and that league IDs alone do not prove professionalism.

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?

Usage is clear for live-game retrieval, and the description explicitly redirects hero-ID resolution to opendota_heroes. It also clarifies that an empty matches list is valid rather than an error. It stops short of explicitly naming opendota_pro_matches or opendota_match as alternatives for non-live or pro-only queries.

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

All Crawlora MCP 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