Crawlora MCP

opendota_league_matches

Read-only

Returns all match summaries for one OpenDota league, including teams, scores, start time and series metadata. Provide a positive league_id from opendota_leagues; optionally provide team_id to keep only matches involving that team. The source list is not paginated; use opendota_match for parsed player statistics.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "league_id": "<league_id>"
    },
    "name": "opendota_league_matches"
  }
}

Input Schema

Name	Required	Description	Default
`team_id`	No	Optional positive team ID; locally keeps matches involving this team.
`league_id`	Yes	Required positive OpenDota league ID from opendota_leagues.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds real behavioral context beyond them: the source list is explicitly not paginated (so a full, potentially large result comes back) and the team filter is described as applied 'locally'. It does not discuss error behavior for an unknown league_id.

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?

Three short sentences with the resource and returned fields front-loaded, followed by parameter guidance and the sibling pointer. Each sentence carries distinct information; nothing is repeated from the name or schema verbatim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described, and the description covers the two things an agent most needs: non-pagination and how team_id filters. Rate limits or behavior on an invalid league_id are unstated, a minor gap for a read-only lookup.

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

Parameters3/5

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

Schema coverage is 100% and both parameters are already documented in the schema, including 'positive ... from opendota_leagues'. The description reinforces positivity and the local-filtering semantics of team_id but adds no format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns all match summaries for one OpenDota league') and enumerates the contents (teams, scores, start time, series metadata). It distinguishes itself from opendota_match by pointing that tool at parsed player statistics, so an agent can separate the two without inspecting schemas.

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?

Gives concrete selection guidance: league_id required and sourced from opendota_leagues, team_id as an optional narrowing filter, and redirects to opendota_match when parsed player stats are wanted. It does not mention the near-identical sibling opendota_league_match_ids (IDs-only), which is the main remaining ambiguity.

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

All Crawlora MCP tools Inspect

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

Need Help?