Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

opendota_league_matches

Fetch all matches for an OpenDota league with teams, scores, and start times, then optionally filter to a specific team.

Instructions

OpenDota matches for one league. Returns the complete match list supplied for one OpenDota league, including match ID, teams, scores, start time and series metadata. Optionally filter locally to matches involving one team; league_id and team_id are echoed. This source route is not paginated and can include completed or scheduled rows; use opendota_match for parsed player statistics.

Input Schema

NameRequiredDescriptionDefault
team_idNoOptional positive team ID; keeps matches where this team is Radiant or Dire
league_idYesPositive league ID from opendota_leagues

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it states the route is not paginated, that rows may be completed or scheduled, and that the team filter is local. It omits permissions/rate-limit context and the exact response envelope, but the behavioral profile is substantial for a read endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then return fields, filter behavior, and the sibling routing hint. Four sentences with little waste, though it is slightly dense and could be tightened.

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?

No output schema or annotations, so the description must cover return values and behavior, which it does: it lists returned fields, describes pagination/filtering behavior, and points elsewhere for parsed stats. Only minor gaps remain (e.g., error behavior), keeping it from a 5.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that filtering by team is applied locally (the result set is the full league list, narrowed client-side) and that league_id/team_id are echoed in output — a genuinely useful behavioral nuance.

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?

Names a specific verb (returns the complete match list) and resource (one OpenDota league), and enumerates the returned fields. It is clearly distinguishable from opendota_match and opendota_league_match_ids because it explicitly scopes to a full league match list with series metadata.

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 a clear routing rule: 'use opendota_match for parsed player statistics', which steers the agent to the right sibling when richer stats are needed. It also explains the optional team filter is applied locally. However, it does not differentiate from other league-oriented siblings such as opendota_league_match_ids or state when not to use this tool.

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